CVE-2026-64452

6lowpan: fix NHC entry use-after-free on error path

HIGH
7.1
CVSS Score
Published: July 25, 2026 at 08:51 AM UTC
Updated: October 19, 2026 at 09:17 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
HIGH7.1
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: 6lowpan: fix NHC entry use-after-free on error path lowpan_nhc_do_uncompression() looks up an NHC descriptor while holding lowpan_nhc_lock. If the descriptor has no uncompress callback, the error path drops the lock before printing nhc->name. lowpan_nhc_del() removes descriptors under the same lock and then relies on synchronize_net() before the owning module can be unloaded. That only waits for net RX RCU readers. lowpan_header_decompress() is also exported and can be reached from callers that are not necessarily covered by the net core RX critical section, for example the Bluetooth 6LoWPAN L2CAP receive path. This leaves a race where one task drops lowpan_nhc_lock in the error path, another task unregisters and frees the matching descriptor after synchronize_net() returns, and the first task then dereferences nhc->name for the warning. With the post-unlock window widened, KASAN reports: BUG: KASAN: slab-use-after-free in lowpan_nhc_do_uncompression+0x1f4/0x220 Read of size 8 lowpan_nhc_do_uncompression lowpan_header_decompress Fix this by printing the warning before dropping lowpan_nhc_lock, so the descriptor name is read while unregister is still excluded. The malformed packet is still rejected with -ENOTSUPP.

Affected

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

4.1 ≤ v < 5.10.2615.11 ≤ v < 5.15.2125.16 ≤ v < 6.1.1786.13 ≤ v < 6.18.396.19 ≤ v < 7.1.46.2 ≤ v < 6.6.1456.7 ≤ v < 6.12.964.192aa7c65d295f3cbb96904afe335f683e55584b8
Vendor states this is fixed in 0beccbcf50de125be5520d0ffc59af4bb8655482 (fixed)
Vendor states this is fixed in 1720db928e5a58ca7d75ac1d514c3b73fd7061a7 (fixed)
Vendor states this is fixed in 593b78bb3c7ef0c6e9ae6fdf5afa80a5f7573168 (fixed)
Vendor states this is fixed in 80b5c8779acee0550845394fb3e5176a398aa24c (fixed)
Vendor states this is fixed in 9c2f5c0829a8c8b904dae36be6d8056b719ac605 (fixed)
Vendor states this is fixed in a8e3a94711134e898c6021a6b77374efa91b3639 (fixed)
Vendor states this is fixed in b713aa0cc344f10f7a9928a230b5f5e780d04078 (fixed)
Vendor states this is fixed in cc27aea4d454abfb385ee2c9499c78b96db9b728 (fixed)
Vendor states this is fixed in 4.1 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.96 (unaffected)
Vendor states this is fixed in 6.18.39 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.4 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.1HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-416

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