CVE-2025-71160

Source
https://cve.org/CVERecord?id=CVE-2025-71160
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-71160.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2025-71160
Downstream
Published
2026-01-23T15:23:58.652Z
Modified
2026-03-13T04:06:21.255671Z
Summary
netfilter: nf_tables: avoid chain re-validation if possible
Details

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 nftchainvalidate():

watchdog: BUG: soft lockup - CPU#1 stuck for 27s! [iptables-nft-re:37547] [..] RIP: 0010:nftchainvalidate+0xcb/0x110 [nftables] [..] nftimmediatevalidate+0x36/0x50 [nftables] nftchainvalidate+0xc9/0x110 [nftables] nftimmediatevalidate+0x36/0x50 [nftables] nftchainvalidate+0xc9/0x110 [nftables] nftimmediatevalidate+0x36/0x50 [nftables] nftchainvalidate+0xc9/0x110 [nftables] nftimmediatevalidate+0x36/0x50 [nftables] nftchainvalidate+0xc9/0x110 [nftables] nftimmediatevalidate+0x36/0x50 [nftables] nftchainvalidate+0xc9/0x110 [nftables] nftimmediatevalidate+0x36/0x50 [nftables] nftchainvalidate+0xc9/0x110 [nftables] nfttablevalidate+0x6b/0xb0 [nftables] nftablesvalidate+0x8b/0xa0 [nftables] nftablescommit+0x1df/0x1eb0 [nftables] [..]

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.

Database specific
{
    "cna_assigner": "Linux",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/71xxx/CVE-2025-71160.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
a654de8fdc1815676ab750e70cab231fc814c29f
Fixed
53de1e6cde8f9b791d9cf61aa0e7b02cf5bbe8b1
Fixed
14fa3d1927f1382f86e3f70a51f26005c8e3cff6
Fixed
09d6074995c186e449979fe6c1b0f1a69cf9bd3b
Fixed
8e1a1bc4f5a42747c08130b8242ebebd1210b32f

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-71160.json"