6lowpan: fix NHC entry use-after-free on error path
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.96, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 92aa7c65d295f3cbb96904afe335f683e55584b8 · fixed in 9c2f5c0829a8c8b904dae36be6d8056b719ac605; From 92aa7c65d295f3cbb96904afe335f683e55584b8 · fixed in 80b5c8779acee0550845394fb3e5176a398aa24c; From 92aa7c65d295f3cbb96904afe335f683e55584b8 · fixed in cc27aea4d454abfb385ee2c9499c78b96db9b728; From 92aa7c65d295f3cbb96904afe335f683e55584b8 · fixed in a8e3a94711134e898c6021a6b77374efa91b3639; From 92aa7c65d295f3cbb96904afe335f683e55584b8 · fixed in 593b78bb3c7ef0c6e9ae6fdf5afa80a5f7573168; From 92aa7c65d295f3cbb96904afe335f683e55584b8 · fixed in 0beccbcf50de125be5520d0ffc59af4bb8655482; From 92aa7c65d295f3cbb96904afe335f683e55584b8 · fixed in b713aa0cc344f10f7a9928a230b5f5e780d04078; From 92aa7c65d295f3cbb96904afe335f683e55584b8 · fixed in 1720db928e5a58ca7d75ac1d514c3b73fd7061a7
- Linux Linux
4.1
- KernelLinux
From 4.1.0 · fixed in 5.10.261; From 5.11.0 · fixed in 5.15.212; From 5.16.0 · fixed in 6.1.178; From 6.2.0 · fixed in 6.6.145; From 6.7.0 · fixed in 6.12.96; From 6.13.0 · fixed in 6.18.39; From 6.19.0 · fixed in 7.1.4
References 8
git.kernel.org
- stable/c/9c2f5c0829a8c8b904dae36be6d8056b719ac605
- stable/c/80b5c8779acee0550845394fb3e5176a398aa24c
- stable/c/cc27aea4d454abfb385ee2c9499c78b96db9b728
- stable/c/a8e3a94711134e898c6021a6b77374efa91b3639
- stable/c/593b78bb3c7ef0c6e9ae6fdf5afa80a5f7573168
- stable/c/0beccbcf50de125be5520d0ffc59af4bb8655482
- stable/c/b713aa0cc344f10f7a9928a230b5f5e780d04078
- stable/c/1720db928e5a58ca7d75ac1d514c3b73fd7061a7