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
CVE-2026-23139 is a Linux kernel availability flaw in netfilter connection counting. Under sufficiently high packet rates, cleanup can be skipped and internal tracking lists can grow without bound. The business risk is denial of service on affected Linux systems, especially systems using netfilter connection-counting controls on exposed network paths.
Executive priority
Treat as high priority for Linux infrastructure on network edges or enforcing connection limits. It is an availability risk with no cited active exploitation, so prioritize patching based on exposure rather than emergency-wide disruption.
Technical view
The issue is in nf_conncount. The kernel updated last_gc whenever a new connection was tracked, even when garbage collection did not run. High packet rate can keep bypassing garbage collection, allowing unbounded list growth. The resolved behavior updates last_gc only after garbage collection is actually performed.
Likely exposure
Exposure is most relevant to affected Linux kernels using netfilter nf_conncount or related connection-limit rules. Internet-facing firewalls, gateways, load balancers, and hosts enforcing connection-count policies should be prioritized. The provided source bundle does not identify affected distributions or appliances.
Exploitation context
The CVE record scores this as network-reachable, low-complexity, unauthenticated, and high availability impact. The source bundle does not report active exploitation, and KEV status is false. The documented trigger is sufficiently high packet rate causing garbage collection bypass and list growth.
Researcher notes
The source evidence is limited to the CVE description and upstream stable commit references. Affected version data in the bundle is not distribution-specific. Researchers should map upstream fixes to deployed kernel builds and avoid assuming exposure without nf_conncount usage evidence.
Mitigation direction
Apply Linux kernel updates containing the referenced stable fixes.
Check distribution or appliance vendor advisories for packaged kernel availability.
Prioritize exposed systems using netfilter connection-counting features.
Use compensating traffic controls where patching is delayed.
Monitor memory pressure and connection-tracking behavior until updated.
Validation and detection
Inventory Linux kernel versions on exposed systems.
Identify hosts using netfilter nf_conncount or connection-limit rules.
Confirm vendor kernel packages include the referenced upstream fixes.
Review monitoring for abnormal memory growth under network load.
Track whether vendor advisories expand affected version guidance.
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.