CVE-2026-23139

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-02-14. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

netfilter: nf_conncount: update last_gc only when GC has been performed

Currently last_gc is being updated everytime a new connection is tracked, that means that it is updated even if a GC wasn't performed. With a sufficiently high packet rate, it is possible to always bypass the GC, causing the list to grow infinitely.

Update the last_gc value only when a GC has been actually performed.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

February 14, 2026

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

netfilter: nf_conncount: update last_gc only when GC has been performed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7811ba452402d58628e68faedf38745b3d485e3c
generic

netfilter: nf_conncount: update last_gc only when GC has been performed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8bdafdf4900040a81422056cabe5e00a37bd101a
generic

netfilter: nf_conncount: update last_gc only when GC has been performed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26a82dce2beee39c43c109d9647e16f49cb02a35
generic

netfilter: nf_conncount: update last_gc only when GC has been performed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3cd717359e56f82f06cbf8279b47a7d79880c6f3
generic

netfilter: nf_conncount: update last_gc only when GC has been performed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9f45588993d7f115280fc726119ca86fba32a811
generic

netfilter: nf_conncount: update last_gc only when GC has been performed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c4cde57c8affdcca5bcff53a1047e15d268bdca1
generic

netfilter: nf_conncount: update last_gc only when GC has been performed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c7c71113ed6d3e2f3aca4c088f22283016ff34f

Vendor Advisories for CVE-2026-23139(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1054.57.1) @ noble2026-06-12ubuntu
ubuntulinux-virtual-6.8 (6.8.0-117.117) @ noble2026-06-12ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-116.116+fips1) @ noble2026-06-12ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1024.24) @ noble2026-06-12ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1059.65+fips1) @ noble2026-06-12ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1054.57~22.04.1) @ jammy2026-06-12ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1056.62) @ noble2026-06-12ubuntu
redhatkernel-0:6.12.0-55.72.1.el10_02026-05-11redhat
linuxKernel @ 6.1.161—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (46 versions)6.1.162-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.69-1~bpo12+1 (10 versions)6.12.69-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (93 versions)6.18.8-1—

Additional Vendor Advisories

(14)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 187 total refreshes for this CVE.

  1. 2026-08-31 00:23 UTCOSV refresh
  2. 2026-08-30 19:17 UTCEPSS rescore
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 14:46 UTCEPSS rescore
  7. 2026-08-25 13:48 UTCEPSS rescore
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-19 17:03 UTCEPSS rescore
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 10:05 UTCEG score recompute
  18. 2026-08-14 10:05 UTCVendor advisory
  19. 2026-08-14 10:05 UTCGHSA enrichment
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 02:23 UTCEG score recompute
  22. 2026-08-13 02:23 UTCVendor advisory
  23. 2026-08-13 02:23 UTCGHSA enrichment
  24. 2026-08-12 13:50 UTCEPSS rescore
  25. 2026-08-11 13:42 UTCEPSS rescore
Show 75 more
  1. 2026-08-11 07:55 UTCEG score recompute
  2. 2026-08-11 07:55 UTCVendor advisory
  3. 2026-08-11 07:54 UTCGHSA enrichment
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-09 14:39 UTCEG score recompute
  6. 2026-08-09 14:39 UTCVendor advisory
  7. 2026-08-09 14:39 UTCGHSA enrichment
  8. 2026-08-09 13:46 UTCEPSS rescore
  9. 2026-08-08 16:37 UTCEPSS rescore
  10. 2026-08-07 21:56 UTCEG score recompute
  11. 2026-08-07 21:56 UTCVendor advisory
  12. 2026-08-07 21:56 UTCGHSA enrichment
  13. 2026-08-06 13:46 UTCEPSS rescore
  14. 2026-08-05 19:17 UTCEPSS rescore
  15. 2026-08-05 12:45 UTCEG score recompute
  16. 2026-08-05 12:45 UTCVendor advisory
  17. 2026-08-05 12:45 UTCGHSA enrichment
  18. 2026-08-04 15:10 UTCEPSS rescore
  19. 2026-08-04 10:38 UTCEPSS rescore
  20. 2026-08-02 20:35 UTCEG score recompute▼ 2.00
  21. 2026-08-02 20:35 UTCVendor advisory
  22. 2026-08-02 20:35 UTCGHSA enrichment
  23. 2026-08-02 02:26 UTCEPSS rescore
  24. 2026-08-01 04:15 UTCEPSS rescore
  25. 2026-07-30 01:30 UTCEPSS rescore
  26. 2026-07-27 14:13 UTCEPSS rescore
  27. 2026-07-26 14:54 UTCEPSS rescore
  28. 2026-07-26 14:54 UTCEPSS rescore
  29. 2026-07-25 14:17 UTCEPSS rescore
  30. 2026-07-25 14:17 UTCEPSS rescore
  31. 2026-07-24 14:17 UTCEPSS rescore
  32. 2026-07-23 14:18 UTCEPSS rescore
  33. 2026-07-23 14:18 UTCEPSS rescore
  34. 2026-07-23 03:06 UTCEG score recompute▲ 2.00
  35. 2026-07-22 14:08 UTCEPSS rescore
  36. 2026-07-21 15:24 UTCEPSS rescore
  37. 2026-07-21 15:24 UTCEPSS rescore
  38. 2026-07-20 17:08 UTCEPSS rescore
  39. 2026-07-19 14:31 UTCEPSS rescore
  40. 2026-07-19 14:31 UTCEPSS rescore
  41. 2026-07-19 02:29 UTCEPSS rescore
  42. 2026-07-19 02:28 UTCEPSS rescore
  43. 2026-07-18 10:04 UTCEPSS rescore
  44. 2026-07-18 10:04 UTCEPSS rescore
  45. 2026-07-17 14:29 UTCOSV refresh
  46. 2026-07-16 17:03 UTCEPSS rescore
  47. 2026-07-16 17:03 UTCEPSS rescore
  48. 2026-07-15 16:57 UTCEPSS rescore
  49. 2026-07-15 16:57 UTCEPSS rescore
  50. 2026-07-15 02:00 UTCEPSS rescore
  51. 2026-07-15 02:00 UTCEPSS rescore
  52. 2026-07-13 22:30 UTCEPSS rescore
  53. 2026-07-13 06:13 UTCEPSS rescore
  54. 2026-07-13 06:13 UTCEPSS rescore
  55. 2026-07-12 05:46 UTCEPSS rescore
  56. 2026-07-12 05:46 UTCEPSS rescore
  57. 2026-07-11 08:27 UTCEPSS rescore
  58. 2026-07-09 19:10 UTCEPSS rescore
  59. 2026-07-08 15:15 UTCEPSS rescore
  60. 2026-07-08 15:15 UTCEPSS rescore
  61. 2026-07-07 13:46 UTCEPSS rescore
  62. 2026-07-06 16:27 UTCEPSS rescore
  63. 2026-07-06 16:27 UTCEPSS rescore
  64. 2026-07-06 02:23 UTCEPSS rescore
  65. 2026-07-06 02:23 UTCEPSS rescore
  66. 2026-07-05 02:30 UTCEPSS rescore
  67. 2026-07-04 06:31 UTCEPSS rescore
  68. 2026-07-04 06:31 UTCEPSS rescore
  69. 2026-07-01 15:06 UTCEPSS rescore
  70. 2026-07-01 15:06 UTCEPSS rescore
  71. 2026-06-30 23:22 UTCEPSS rescore
  72. 2026-06-30 23:22 UTCEPSS rescore
  73. 2026-06-29 14:06 UTCEPSS rescore
  74. 2026-06-29 13:02 UTCOSV refresh
  75. 2026-06-28 14:07 UTCEPSS rescore

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2026-23139?
CVE-2026-23139 is a medium vulnerability published on February 14, 2026. In the Linux kernel, the following vulnerability has been resolved: netfilter: nfconncount: update lastgc only when GC has been performed Currently last_gc is being updated everytime a new connection is tracked, that means that it is updated even if a GC wasn't performed. With a sufficiently high…
When was CVE-2026-23139 disclosed?
CVE-2026-23139 was first published in the National Vulnerability Database on February 14, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23139 actively exploited?
CVE-2026-23139 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.8% of all scored CVEs.
What is the CVSS score of CVE-2026-23139?
CVE-2026-23139 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23139?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23139, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-23139

Explore →

Is Your Infrastructure Affected by CVE-2026-23139?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs