CVE-2026-23139: netfilter: nf_conncount: update last_gc only when GC has been performed
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.
Security readout for executives and security teams
Plain-English summary
A Linux netfilter connection-counting flaw can prevent cleanup during sustained high packet rates. The tracked-connection list may then grow without bound, exhausting resources and disrupting service. The supplied CVSS score is 7.5, reflecting remotely triggerable availability impact without privileges or user interaction.
Executive priority
Treat as a high-priority availability risk for exposed Linux firewalls, gateways, and servers using the affected function. Patch promptly after normal compatibility testing, with fastest attention to systems receiving untrusted high-volume traffic. Evidence supplied does not justify an emergency active-exploitation declaration.
Technical view
In nf_conncount, last_gc was updated whenever a connection was tracked, even when garbage collection did not run. Sufficiently frequent traffic could continually defer collection, allowing the internal list to grow indefinitely. The referenced stable-kernel commits change last_gc updates to occur only after garbage collection is performed.
Likely exposure
Exposure is most likely on systems running an affected Linux kernel and using nf_conncount for traffic reachable at high packet rates. The bundle lists affected kernel versions, but distribution kernels may backport fixes; assess package builds against vendor advisories or referenced commits rather than version numbers alone.
Exploitation context
The condition is network reachable, low complexity, requires no privileges or user interaction, and affects availability. The supplied record says KEV is false and provides no evidence of active exploitation. Absence from KEV does not establish that exploitation has never occurred.
Researcher notes
The failure is a garbage-collection timing defect rather than a confidentiality or integrity issue. The CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Precise affected ranges and distribution backports are not fully resolved by the bundle, so commit-level or vendor-package verification is important.
Mitigation direction
Install a distribution kernel containing the applicable referenced nf_conncount fix.
Check Linux distribution advisories for backported-fix and reboot requirements.
Prioritize internet-facing systems using netfilter connection-counting rules.
Until patched, apply appropriate upstream traffic controls to limit sustained abusive packet rates.
Validation and detection
Inventory running kernel builds and compare them with distribution security advisories.
Verify the installed kernel contains the applicable referenced stable commit or documented backport.
Review netfilter configuration for connection-counting rules using nf_conncount.
Confirm systems booted into the remediated kernel after package installation.
Monitor exposed systems for abnormal resource growth and availability degradation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-23139 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
8Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.