CVE-2026-64452
CVE CVE-2026-64452EUVD EUVD-2026-48796Published 2026-07-25T08:51:21.000ZLast changed 2026-08-05T12:42:15.000ZCVSS 7.1
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 92aa7c65d295f3cbb96904afe335f683e55584b8 <9c2f5c0829a8c8b904dae36be6d8056b719ac605; 4.1; patch: 7.2-rc1; patch: 0; patch: 7.1.4; 92aa7c65d295f3cbb96904afe335f683e55584b8 <1720db928e5a58ca7d75ac1d514c3b73fd7061a7; 92aa7c65d295f3cbb96904afe335f683e55584b8 <80b5c8779acee0550845394fb3e5176a398aa24c; 92aa7c65d295f3cbb96904afe335f683e55584b8 <a8e3a94711134e898c6021a6b77374efa91b3639; 92aa7c65d295f3cbb96904afe335f683e55584b8 <593b78bb3c7ef0c6e9ae6fdf5afa80a5f7573168; 92aa7c65d295f3cbb96904afe335f683e55584b8 <b713aa0cc344f10f7a9928a230b5f5e780d04078; patch: 6.1.178; patch: 6.6.145; 92aa7c65d295f3cbb96904afe335f683e55584b8 <cc27aea4d454abfb385ee2c9499c78b96db9b728; patch: 5.10.261; patch: 5.15.212; patch: 6.12.96; patch: 6.18.39; 92aa7c65d295f3cbb96904afe335f683e55584b8 <0beccbcf50de125be5520d0ffc59af4bb8655482
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.