CVE-2026-72247: netfilter: nf_conncount: fix zone comparison in tuple dedup
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.69% (FIRST EPSS); higher than 52.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 35a56e2a46b90e6bd4ca816b80e9cb8d20dfc3ce, 3cd9a5792cbea81139c24320986dd0db69e9b5d0, 4.15.
Low priority for now. Upgrade to Linux Linux 35a56e2a46b90e6bd4ca816b80e9cb8d20dfc3ce, 3cd9a5792cbea81139c24320986dd0db69e9b5d0, 4.15 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conncount: fix zone comparison in tuple dedup The "already exists" dedup logic in __nf_conncount_add() decides whether a connection has already been counted and can be skipped instead of incrementing the connlimit count. It compares the conntrack zone of a list entry with the zone of the connection being added using nf_ct_zone_id() and nf_ct_zone_equal(), passing conn->zone.dir or zone->dir as the direction argument. Those helpers take enum ip_conntrack_dir values: IP_CT_DIR_ORIGINAL is 0 and IP_CT_DIR_REPLY is 1. However, zone->dir is a u8 bitmask: NF_CT_ZONE_DIR_ORIG is 1, NF_CT_ZONE_DIR_REPL is 2 and NF_CT_DEFAULT_ZONE_DIR is 3. Passing that bitmask as the enum direction shifts the meaning of every non-zero value. An ORIG-only zone passes 1 and is tested as REPLY, while REPL-only and default zones pass 2 or 3 and test bits beyond the valid direction range. In those cases nf_ct_zone_id() can fall back to NF_CT_DEFAULT_ZONE_ID instead of using the real zone id, so different zones can be treated as equal and dedup collapses to tuple equality alone. nf_conncount stores and compares the original-direction tuple for a connection. If an skb already has an attached conntrack entry, get_ct_or_tuple_from_skb() explicitly copies ct->tuplehash[IP_CT_DIR_ORIGINAL].tuple, regardless of the packet's ctinfo. Therefore the zone comparison in the tuple dedup path must use IP_CT_DIR_ORIGINAL as well; the zone direction bitmask describes where a zone id applies, not which direction this conncount tuple represents. Fix the two dedup comparisons by passing IP_CT_DIR_ORIGINAL directly. Do not special-case NF_CT_DEFAULT_ZONE_DIR and do not compare raw zone ids: using the existing helpers with IP_CT_DIR_ORIGINAL preserves the direction-aware NF_CT_DEFAULT_ZONE_ID fallback. A default bidirectional zone contains the ORIG bit, so it naturally returns the real zone id; reply-only zones continue to fall back for original-direction tuple comparisons.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.6% · 52th percentile
- CWE
- —
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 525e1dffed8711973f77412729621098a95238e5, 75af3d78168e654a5cd8bbc4c774f97be836165f, 4.18affected
- 21ba8847f857028dc83a0f341e16ecc616e34740 and later · before 82fc35e0da9a91db9a034f8311f18f77a599ae3faffected · git
- 21ba8847f857028dc83a0f341e16ecc616e34740 and later · before 78b5d6dbc860776161f9e9206b06ff8a01f531abaffected · git
- 21ba8847f857028dc83a0f341e16ecc616e34740 and later · before 4f30a89c0ed2418719a1144881c2635b940b543daffected · git
- 21ba8847f857028dc83a0f341e16ecc616e34740 and later · before 7bdc3c0985ecf17b957811fedcc684acdf698accaffected · git
- 21ba8847f857028dc83a0f341e16ecc616e34740 and later · before 35a56e2a46b90e6bd4ca816b80e9cb8d20dfc3ceaffected · git
- 21ba8847f857028dc83a0f341e16ecc616e34740 and later · before 3cd9a5792cbea81139c24320986dd0db69e9b5d0affected · git
- 21ba8847f857028dc83a0f341e16ecc616e34740 and later · before 6ff07ac5405bea4d4ead3559fc123f987576424aaffected · git
- 21ba8847f857028dc83a0f341e16ecc616e34740 and later · before f62c41b4910e65da396ec9a8c40c1fe7fe82e449affected · git
- 4.14.92 and later · before 4.15affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72243Aug 15, 2026 · selinux: check connect-related permissions on TCP Fast Open33Monitor
- ← EarlierCVE-2026-72244Aug 15, 2026 · gpu/buddy: bail out of try_harder when alignment cannot be honoured31Monitor
- Later →CVE-2026-72250Aug 15, 2026 · netfilter: nf_conntrack_reasm: guard mac_header adjustment after IPv6 defrag31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 35a56e2a46b90e6bd4ca816b80e9cb8d20dfc3ce | Vendor (CNA) |
| Linux Linux | 3cd9a5792cbea81139c24320986dd0db69e9b5d0 | Vendor (CNA) |
| Linux Linux | 4.15 | Vendor (CNA) |
| Linux Linux | 4f30a89c0ed2418719a1144881c2635b940b543d | Vendor (CNA) |
| Linux Linux | 6ff07ac5405bea4d4ead3559fc123f987576424a | Vendor (CNA) |
| Linux Linux | 78b5d6dbc860776161f9e9206b06ff8a01f531ab | Vendor (CNA) |
| Linux Linux | 7bdc3c0985ecf17b957811fedcc684acdf698acc | Vendor (CNA) |
| Linux Linux | 82fc35e0da9a91db9a034f8311f18f77a599ae3f | Vendor (CNA) |
| Linux Linux | f62c41b4910e65da396ec9a8c40c1fe7fe82e449 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/3cd9a5792cbea81139c24320986dd0db69e9b5d0
- git.kernel.org/stable/c/4f30a89c0ed2418719a1144881c2635b940b543d
- git.kernel.org/stable/c/6ff07ac5405bea4d4ead3559fc123f987576424a
- git.kernel.org/stable/c/78b5d6dbc860776161f9e9206b06ff8a01f531ab
- git.kernel.org/stable/c/7bdc3c0985ecf17b957811fedcc684acdf698acc
- git.kernel.org/stable/c/82fc35e0da9a91db9a034f8311f18f77a599ae3f
- git.kernel.org/stable/c/f62c41b4910e65da396ec9a8c40c1fe7fe82e449
Vendor advisories and official records. Exploit/PoC links are deliberately left out.