CVE-2026-74565: Linux kernel · netfilter: nf_tables: make nft_object rhltable per table
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.8 High · fixed in f4f699790590bd0896c48a71e9232a65198f92f0 : patch Linux kernel soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% 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 cannot 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 f4f699790590bd0896c48a71e9232a65198f92f0, 71714a2cec6c6d79bbd425ad968f9d6a3e4a2066, 1948e4f85b855618b5b9a27265f98d816f4cb7cb +4
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: make nft_object rhltable per table The nft_object rhltable is global, this allows for accessing objects that are being dismangled from lookup path by other existing netns. Given the nft_obj_destroy() releases the object inmediately, this might lead to use-after-free of these objects that are being released. Make the existing rhltable per table to address this issue to deal with with the nft_rcv_nl_event() path too. Update nft_obj_lookup() to take the table as non-const, otherwise, compiler complains when passing the objname_ht to rhltable_lookup().
References
- git.kernel.org/stable/c/4b549d32d34ee765527e63726bb1af984876e776 (opens in a new tab)
- git.kernel.org/stable/c/523c881661dde67efb44fce38c8eed50a72a57c1 (opens in a new tab)
- git.kernel.org/stable/c/71714a2cec6c6d79bbd425ad968f9d6a3e4a2066 (opens in a new tab)
- git.kernel.org/stable/c/1948e4f85b855618b5b9a27265f98d816f4cb7cb (opens in a new tab)
- git.kernel.org/stable/c/63ba12b664a2cd3220ed43e22c717715f4cc2ae8 (opens in a new tab)
- git.kernel.org/stable/c/7d4789b58761d9d48d9b5f5e7e0a510c3bbfb3af (opens in a new tab)
- git.kernel.org/stable/c/f4f699790590bd0896c48a71e9232a65198f92f0 (opens in a new tab)