Skip to main content
VulnerabilityPublished Updated

CVE-2026-23399: Linux kernel · nf_tables: nft_dynset: fix possible stateful expression memleak in error path

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in eb7bf413e59945df03d4567b73ce464eebe2f4ea : update Linux kernel when convenient.

Data as of 5 Nov 2026, 22:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in eb7bf413e59945df03d4567b73ce464eebe2f4ea, e6661add2d9c6913e1dad97336595e23a2bed195, d1354873cbe3b344899c4311ac05897fd83e3f21 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 563125a73ac30d7036ae69ca35c40500562c1de4, < eb7bf413e59945df03d4567b73ce464eebe2f4ea
Fixed in
  • eb7bf413e59945df03d4567b73ce464eebe2f4ea
LinuxLinuxAffected
  • ≥ 563125a73ac30d7036ae69ca35c40500562c1de4, < e6661add2d9c6913e1dad97336595e23a2bed195
Fixed in
  • e6661add2d9c6913e1dad97336595e23a2bed195
LinuxLinuxAffected
  • ≥ 563125a73ac30d7036ae69ca35c40500562c1de4, < d1354873cbe3b344899c4311ac05897fd83e3f21
Fixed in
  • d1354873cbe3b344899c4311ac05897fd83e3f21
LinuxLinuxAffected
  • ≥ 563125a73ac30d7036ae69ca35c40500562c1de4, < c88a9fd26cee365bec932196f76175772a941cca
Fixed in
  • c88a9fd26cee365bec932196f76175772a941cca
LinuxLinuxAffected
  • ≥ 563125a73ac30d7036ae69ca35c40500562c1de4, < 31641c682db73353e4647e40735c7f2a75ff58ef
Fixed in
  • 31641c682db73353e4647e40735c7f2a75ff58ef
LinuxLinuxAffected
  • ≥ 563125a73ac30d7036ae69ca35c40500562c1de4, < 4357dbb1d9c35ca0b4443d71c98a48e6666f7689
Fixed in
  • 4357dbb1d9c35ca0b4443d71c98a48e6666f7689

Description

In the Linux kernel, the following vulnerability has been resolved: nf_tables: nft_dynset: fix possible stateful expression memleak in error path If cloning the second stateful expression in the element via GFP_ATOMIC fails, then the first stateful expression remains in place without being released.   unreferenced object (percpu) 0x607b97e9cab8 (size 16):     comm "softirq", pid 0, jiffies 4294931867     hex dump (first 16 bytes on cpu 3):       00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     backtrace (crc 0):       pcpu_alloc_noprof+0x453/0xd80       nft_counter_clone+0x9c/0x190 [nf_tables]       nft_expr_clone+0x8f/0x1b0 [nf_tables]       nft_dynset_new+0x2cb/0x5f0 [nf_tables]       nft_rhash_update+0x236/0x11c0 [nf_tables]       nft_dynset_eval+0x11f/0x670 [nf_tables]       nft_do_chain+0x253/0x1700 [nf_tables]       nft_do_chain_ipv4+0x18d/0x270 [nf_tables]       nf_hook_slow+0xaa/0x1e0       ip_local_deliver+0x209/0x330

References

Community reviews

Loading reviews…