Skip to main content
VulnerabilityPublished Updated

CVE-2026-72320: Linux kernel · netfilter: nft_lookup: fix catchall element handling with inverted lookups

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical · fixed in ef0c7d4b04a0e6ad175323c24bc84e11470dd79d : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in ef0c7d4b04a0e6ad175323c24bc84e11470dd79d, e6107a4c74b54cb33e3bce162a63048ae5a6b198, 238c612357b5a25f03eacf356f95034f8551f218 +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ aaa31047a6d25da0fa101da1ed544e1247949b40, < ef0c7d4b04a0e6ad175323c24bc84e11470dd79d
Fixed in
  • ef0c7d4b04a0e6ad175323c24bc84e11470dd79d
LinuxLinuxAffected
  • ≥ aaa31047a6d25da0fa101da1ed544e1247949b40, < e6107a4c74b54cb33e3bce162a63048ae5a6b198
Fixed in
  • e6107a4c74b54cb33e3bce162a63048ae5a6b198
LinuxLinuxAffected
  • ≥ aaa31047a6d25da0fa101da1ed544e1247949b40, < 238c612357b5a25f03eacf356f95034f8551f218
Fixed in
  • 238c612357b5a25f03eacf356f95034f8551f218
LinuxLinuxAffected
  • ≥ aaa31047a6d25da0fa101da1ed544e1247949b40, < 65d35cb555f40529a9edc6bf4beaa3bee917f015
Fixed in
  • 65d35cb555f40529a9edc6bf4beaa3bee917f015
LinuxLinuxAffected
  • ≥ aaa31047a6d25da0fa101da1ed544e1247949b40, < 0ab8880865f9678eb6174e72c1fc4712e44c745c
Fixed in
  • 0ab8880865f9678eb6174e72c1fc4712e44c745c
LinuxLinuxAffected
  • =5.13
Fixed in–

Description

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().

References

Community reviews

Loading reviews…