CVE-2026-72392

ipv6: fib6: fix NULL deref in fib6_walk_continue() on multi-batch dump

N/A
Published: August 15, 2026 at 05:56 AM UTC
Updated: August 19, 2026 at 05:21 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: ipv6: fib6: fix NULL deref in fib6_walk_continue() on multi-batch dump inet6_dump_fib() saves its progress in cb->args[1] as a positional index within the current hash chain. Between batches, a concurrent fib6_new_table() can insert a new table at the chain head, shifting all existing entries. The saved index then lands on a different table, causing fib6_dump_table() to set w->root to the wrong table while w->node still points into the previous one. fib6_walk_continue() dereferences w->node->parent (NULL) and panics: BUG: kernel NULL pointer dereference, address: 0000000000000008 RIP: 0010:fib6_walk_continue+0x6e/0x170 Call Trace: <TASK> fib6_dump_table.isra.0+0xc5/0x240 inet6_dump_fib+0xf6/0x420 rtnl_dumpit+0x30/0xa0 netlink_dump+0x15b/0x460 netlink_recvmsg+0x1d6/0x2a0 ____sys_recvmsg+0x17a/0x190 Fix by storing tb->tb6_id in cb->args[1] instead of a positional index. On resume, skip entries until the id matches; a concurrent head-insert can never match the saved id, so the walker always resumes on the correct table.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.19 ≤ v < 5.10.2652.6.19 ≤ v < 5.15.2122.6.19 ≤ v < 6.1.1832.6.19 ≤ v < 6.12.972.6.19 ≤ v < 6.18.402.6.19 ≤ v < 6.6.1512.6.19 ≤ v < 7.1.52.6.19 ≤ v < 7.21b43af5480c351dbcb2eef478bafe179cbeb6e832.6.19
Vendor states this is fixed in 059efb48dd746518898faaa9b965511009b59639 (fixed)
Vendor states this is fixed in 110ccbd28c9444866fcc84ba96a2ad64fa6e95ae (fixed)
Vendor states this is fixed in 27210d433a8c5fe6bf7278a04bbaeb49a81d0290 (fixed)
Vendor states this is fixed in 89f9c5fee3c64c5cabc34e65599308fd3c879cf9 (fixed)
Vendor states this is fixed in 9facb861dc6b9b9ea9793ef5032a9a826f7a4229 (fixed)
Vendor states this is fixed in cb90a774a9c6c46961a44949a246fbb61f5f934c (fixed)
Vendor states this is fixed in d8a01d27873e04bebd357dc87859aa756e0b28b2 (fixed)
Vendor states this is fixed in ee73a32dd258d4af66831ff006b771e19812b322 (fixed)
Vendor states this is fixed in 2.6.19 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.151 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card