Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

CVE-2025-71160— netfilter: nf_tables: avoid chain re-validation if possible

EPSS 0.01% · P1
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2025-71160

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
netfilter: nf_tables: avoid chain re-validation if possible
Source: NVD (National Vulnerability Database)
Vulnerability 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.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于nft_chain_validate函数可能陷入递归循环，可能导致CPU软锁定。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux a654de8fdc1815676ab750e70cab231fc814c29f ~ 53de1e6cde8f9b791d9cf61aa0e7b02cf5bbe8b1 -
LinuxLinux 4.18 -

II. Public POCs for CVE-2025-71160

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2025-71160

请登录查看更多情报信息。

Same Patch Batch · Linux · 2026-01-23 · 34 CVEs total

CVE-2026-229849.8 CRITICALlibceph: prevent potential out-of-bounds reads in handle_auth_done()
CVE-2026-229887.8 HIGHarp: do not assume dev_hard_header() does not change skb->head
CVE-2026-229807.8 HIGHnfsd: provide locking for v4_end_grace
CVE-2026-229927.5 HIGHlibceph: return the handler error from mon_handle_auth_done()
CVE-2026-229917.5 HIGHlibceph: make free_choose_arg_map() resilient to partial allocation
CVE-2026-229907.5 HIGHlibceph: replace overzealous BUG_ON in osdmap_apply_incremental()
CVE-2026-22993idpf: Fix RSS LUT NULL ptr issue after soft reset
CVE-2026-22989nfsd: check that server is running in unlock_filesystem
CVE-2026-22979net: fix memory leak in skb_segment_list for GRO packets
CVE-2026-22987net/sched: act_api: avoid dereferencing ERR_PTR in tcf_idrinfo_destroy
CVE-2026-22986gpiolib: fix race condition for gdev->srcu
CVE-2026-22985idpf: Fix RSS LUT NULL pointer crash on early ethtool operations
CVE-2026-22994bpf: Fix reference count leak in bpf_prog_test_run_xdp()
CVE-2026-22983net: do not write to msg_get_inq in callee
CVE-2026-22982net: mscc: ocelot: Fix crash when adding interface under a lag
CVE-2026-22981idpf: detach and close netdevs while handling a reset
CVE-2026-22995ublk: fix use-after-free in ublk_partition_scan_work
CVE-2025-71145usb: phy: isp1301: fix non-OF device reference imbalance
CVE-2026-22978wifi: avoid kernel-infoleak from struct iw_point
CVE-2025-71161dm-verity: disable recursive forward error correction

Showing top 20 of 34 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

Same product: Linux
Same vendor: Linux

V. Comments for CVE-2025-71160

No comments yet

Leave a comment