What happened
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
Affected versions
Linux: 563125a73ac30d7036ae69ca35c40500562c1de4 through before eb7bf413e59945df03d4567b73ce464eebe2f4ea (git); 563125a73ac30d7036ae69ca35c40500562c1de4 through before 4357dbb1d9c35ca0b4443d71c98a48e6666f7689 (git); 563125a73ac30d7036ae69ca35c40500562c1de4 through before e6661add2d9c6913e1dad97336595e23a2bed195 (git); 563125a73ac30d7036ae69ca35c40500562c1de4 through before d1354873cbe3b344899c4311ac05897fd83e3f21 (git); 563125a73ac30d7036ae69ca35c40500562c1de4 through before 31641c682db73353e4647e40735c7f2a75ff58ef (git); 563125a73ac30d7036ae69ca35c40500562c1de4 through before c88a9fd26cee365bec932196f76175772a941cca (git); 563125a73ac30d7036ae69ca35c40500562c1de4 through before 0548a13b5a145b16e4da0628b5936baf35f51b43 (git); 5.11; V3.1.6 through before * (custom) Fixed: See vendor advisory.
Why it matters
Review the vendor advisory and exposure of the affected product to determine operational impact.
Detection & mitigation
- Apply vendor-provided updates or mitigations.
- Review affected product exposure and access logs.
Public PoC references
No public PoC reference has passed the current publication threshold.