CVE-2025-71160: Linux kernel · netfilter: nf_tables: avoid chain re-validation if possible
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 6.8.0-1057.60~22.04.1 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 16:39 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.8.0-1057.60~22.04.1, 6.8.0-1059.65~22.04.1, 6.8.0-1058.65~22.04.1 +37
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 23 Jan 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.
Patches and advisories
- ubuntu.com/security/notices/USN-8278-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8289-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8296-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8296-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8289-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8278-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8393-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8440-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8499-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8570-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8594-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8604-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 25.10linuxpkg:deb/ubuntu/linux?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 25.10linux-oraclepkg:deb/ubuntu/linux-oracle?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: avoid chain re-validation if possible Hamza Mahfooz reports cpu soft lock-ups in nft_chain_validate(): watchdog: BUG: soft lockup - CPU#1 stuck for 27s! [iptables-nft-re:37547] [..] RIP: 0010:nft_chain_validate+0xcb/0x110 [nf_tables] [..] nft_immediate_validate+0x36/0x50 [nf_tables] nft_chain_validate+0xc9/0x110 [nf_tables] nft_immediate_validate+0x36/0x50 [nf_tables] nft_chain_validate+0xc9/0x110 [nf_tables] nft_immediate_validate+0x36/0x50 [nf_tables] nft_chain_validate+0xc9/0x110 [nf_tables] nft_immediate_validate+0x36/0x50 [nf_tables] nft_chain_validate+0xc9/0x110 [nf_tables] nft_immediate_validate+0x36/0x50 [nf_tables] nft_chain_validate+0xc9/0x110 [nf_tables] nft_immediate_validate+0x36/0x50 [nf_tables] nft_chain_validate+0xc9/0x110 [nf_tables] nft_table_validate+0x6b/0xb0 [nf_tables] nf_tables_validate+0x8b/0xa0 [nf_tables] nf_tables_commit+0x1df/0x1eb0 [nf_tables] [..] Currently nf_tables will traverse the entire table (chain graph), starting from the entry points (base chains), exploring all possible paths (chain jumps). But there are cases where we could avoid revalidation. Consider: 1 input -> j2 -> j3 2 input -> j2 -> j3 3 input -> j1 -> j2 -> j3 Then the second rule does not need to revalidate j2, and, by extension j3, because this was already checked during validation of the first rule. We need to validate it only for rule 3. This is needed because chain loop detection also ensures we do not exceed the jump stack: Just because we know that j2 is cycle free, its last jump might now exceed the allowed stack size. We also need to update all reachable chains with the new largest observed call depth. Care has to be taken to revalidate even if the chain depth won't be an issue: chain validation also ensures that expressions are not called from invalid base chains. For example, the masquerade expression can only be called from NAT postrouting base chains. Therefore we also need to keep record of the base chain context (type, hooknum) and revalidate if the chain becomes reachable from a different hook location.
References
- ubuntu.com/security/CVE-2025-71160 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2025-71160 (opens in a new tab)
- git.kernel.org/linus/8e1a1bc4f5a42747c08130b8242ebebd1210b32f (opens in a new tab)
- git.kernel.org/stable/c/09d6074995c186e449979fe6c1b0f1a69cf9bd3b (opens in a new tab)
- git.kernel.org/stable/c/14fa3d1927f1382f86e3f70a51f26005c8e3cff6 (opens in a new tab)
- git.kernel.org/stable/c/53de1e6cde8f9b791d9cf61aa0e7b02cf5bbe8b1 (opens in a new tab)
- git.kernel.org/stable/c/8e1a1bc4f5a42747c08130b8242ebebd1210b32f (opens in a new tab)
- ubuntu.com/security/notices/USN-8278-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8289-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8296-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8296-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8289-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8278-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8393-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8440-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8499-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8570-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8594-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8604-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8605-1 (opens in a new tab)