Skip to main content

Linux Kernel CVE-2026-72320

| EUVDEUVD-2026-59219 CRITICAL
2026-08-15 Linux GHSA-xm9x-r949-vc7p
9.1
CVSS 3.1 · Vendor: Linux
Share

Severity by source

Vendor (Linux) PRIMARY
9.1 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
vuln.today AI
7.0 HIGH

Remote packets trigger it (AV:N) but only against a specific inverted-interval-set ruleset, so AC:H; impact is a firewall-policy integrity bypass (I:H) with indirect confidentiality (C:L) and possible wrongful drops (A:L).

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:L
4.0 AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N
SUSE
7.0 HIGH
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Red Hat
7.0 HIGH
qualitative

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

5
Analysis Generated
Aug 17, 2026 - 08:25 vuln.today
CVSS changed
Aug 17, 2026 - 06:22 NVD
9.1 (CRITICAL)
Patch available
Aug 15, 2026 - 07:20 EUVD
CVE Published
Aug 15, 2026 - 05:55 cve.org
CRITICAL 9.1
CVE Published
Aug 15, 2026 - 05:55 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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

netfilter: nft_lookup: fix catchall element handling with inverted lookups

nft_lookup_eval() decides whether a lookup matched (found) from the direct set lookup and priv->invert before falling back to the catchall element used by interval sets (e.g. nft_set_rbtree) for the open-ended default range. Since found is never recomputed after ext is replaced by the catchall lookup, inverted lookups (NFT_LOOKUP_F_INV, "!= @set") can wrongly match or wrongly skip the catchall element, producing the wrong verdict. Fold the catchall lookup into ext before computing found, matching the order already used by nft_objref_map_eval().

AnalysisAI

Firewall policy bypass in the Linux kernel's netfilter nftables subsystem allows remote attackers to evade packet-filtering rules that use inverted set lookups. The flaw lives in nft_lookup_eval(), where the match result for negated lookups ('!= @set') is computed before the catchall element used by interval sets is folded in, so rules resolve to the wrong verdict. It affects the nf_tables classifier across a wide range of kernel branches; there is no public exploit identified at time of analysis and EPSS probability is low (0.21%).

Technical ContextAI

The vulnerable code is in net/netfilter/nft_lookup.c, the generic set-lookup expression used by nftables rules of the form 'meta ... @set' and its negation '!= @set'. Interval sets (typically backed by nft_set_rbtree) use a synthetic catchall element to represent the open-ended default range. nft_lookup_eval() first performs a direct set lookup, combines the outcome with priv->invert to derive the boolean 'found', and only afterward substitutes the catchall element into 'ext'. Because 'found' is never recomputed after that substitution, the inversion (NFT_LOOKUP_F_INV) is applied to the pre-catchall state, so the rule matches when it should not or skips when it should match. The fix reorders the logic to fold the catchall result into 'ext' before evaluating 'found', mirroring the correct ordering already present in nft_objref_map_eval(). No CWE was assigned, but the root cause is a logic/ordering defect in a security decision path - an incorrect-comparison / stale-state class of bug rather than memory corruption. The CPE data identifies the affected product only generically as cpe:2.3:a:linux:linux, i.e. the mainline kernel.

RemediationAI

Vendor-released patch: upgrade to a fixed stable kernel - 6.12.97, 6.18.40, 7.1.5, or 7.2-rc3 (or your distribution's backported equivalent), applying the commits referenced at https://git.kernel.org/stable/c/238c612357b5a25f03eacf356f95034f8551f218 and the sibling stable commits, per https://nvd.nist.gov/vuln/detail/CVE-2026-72320. Because the fix is a small, self-contained logic reordering, distribution kernel updates are the cleanest path. If you cannot patch immediately, the concrete compensating control is to audit nftables rulesets and remove or rewrite inverted set lookups ('!= @set') that operate against interval/catchall sets - for example, replace a negated interval-set match with an explicit positive match plus a default-policy fallthrough, which avoids the buggy code path at the cost of more verbose and potentially slower rules. Do not rely on this as a permanent fix, and re-verify verdicts with test traffic after any rewrite, since the whole point of the bug is that the rule silently evaluates to the wrong result.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 16.0 Not-Affected

Share

CVE-2026-72320 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy