CVE-2026-72392: ipv6: fib6: fix NULL deref in fib6_walk_continue() on multi-batch dump
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 059efb48dd746518898faaa9b965511009b59639, 110ccbd28c9444866fcc84ba96a2ad64fa6e95ae, 27210d433a8c5fe6bf7278a04bbaeb49a81d0290; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
Low priority for now. Upgrade to Linux Linux 059efb48dd746518898faaa9b965511009b59639, 110ccbd28c9444866fcc84ba96a2ad64fa6e95ae, 27210d433a8c5fe6bf7278a04bbaeb49a81d0290; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 15, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.19affected
- 1b43af5480c351dbcb2eef478bafe179cbeb6e83 and later · before ee73a32dd258d4af66831ff006b771e19812b322affected · git
- 1b43af5480c351dbcb2eef478bafe179cbeb6e83 and later · before 89f9c5fee3c64c5cabc34e65599308fd3c879cf9affected · git
- 1b43af5480c351dbcb2eef478bafe179cbeb6e83 and later · before cb90a774a9c6c46961a44949a246fbb61f5f934caffected · git
- 1b43af5480c351dbcb2eef478bafe179cbeb6e83 and later · before 27210d433a8c5fe6bf7278a04bbaeb49a81d0290affected · git
- 1b43af5480c351dbcb2eef478bafe179cbeb6e83 and later · before 059efb48dd746518898faaa9b965511009b59639affected · git
- 1b43af5480c351dbcb2eef478bafe179cbeb6e83 and later · before d8a01d27873e04bebd357dc87859aa756e0b28b2affected · git
- 1b43af5480c351dbcb2eef478bafe179cbeb6e83 and later · before 110ccbd28c9444866fcc84ba96a2ad64fa6e95aeaffected · git
- 1b43af5480c351dbcb2eef478bafe179cbeb6e83 and later · before 9facb861dc6b9b9ea9793ef5032a9a826f7a4229affected · git
- before 2.6.19not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72389Aug 15, 2026 · bridge: stp: Fix a potential use-after-free when deleting a bridge31Monitor
- ← EarlierCVE-2026-72390Aug 15, 2026 · net/sched: sch_teql: Introduce slaves_lock to avoid race condition and UAF31Monitor
- Later →CVE-2026-72395Aug 15, 2026 · hwmon: (pmbus) Fix passing events to regulator core28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 059efb48dd746518898faaa9b965511009b59639 | Vendor (CNA) |
| Linux Linux | 110ccbd28c9444866fcc84ba96a2ad64fa6e95ae | Vendor (CNA) |
| Linux Linux | 27210d433a8c5fe6bf7278a04bbaeb49a81d0290 | Vendor (CNA) |
| Linux Linux | 89f9c5fee3c64c5cabc34e65599308fd3c879cf9 | Vendor (CNA) |
| Linux Linux | 9facb861dc6b9b9ea9793ef5032a9a826f7a4229 | Vendor (CNA) |
| Linux Linux | cb90a774a9c6c46961a44949a246fbb61f5f934c | Vendor (CNA) |
| Linux Linux | d8a01d27873e04bebd357dc87859aa756e0b28b2 | Vendor (CNA) |
| Linux Linux | ee73a32dd258d4af66831ff006b771e19812b322 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.152.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/110ccbd28c9444866fcc84ba96a2ad64fa6e95ae
- git.kernel.org/stable/c/27210d433a8c5fe6bf7278a04bbaeb49a81d0290
- git.kernel.org/stable/c/89f9c5fee3c64c5cabc34e65599308fd3c879cf9
- git.kernel.org/stable/c/9facb861dc6b9b9ea9793ef5032a9a826f7a4229
- git.kernel.org/stable/c/cb90a774a9c6c46961a44949a246fbb61f5f934c
- git.kernel.org/stable/c/d8a01d27873e04bebd357dc87859aa756e0b28b2
- git.kernel.org/stable/c/ee73a32dd258d4af66831ff006b771e19812b322
Vendor advisories and official records. Exploit/PoC links are deliberately left out.