CVE-2026-64452

Vulnérabilité élevée dans Linux (Linux)

CVSS 7.1 · Élevée
EPSS 0.2%
Linux•Linux•Versions : <=6.1.*, <=6.12.*, <593b78bb3c7ef0c6e9ae6fdf5afa80a5f7573168, 6.18.39, 0, <9c2f5c0829a8c8b904dae36be6d8056b719ac605, <4.1, <cc27aea4d454abfb385ee2c9499c78b96db9b728, <=7.1.*, 7.1.4, 6.1.178, 92aa7c65d295f3cbb96904afe335f683e55584b8, <=5.10.*, <=6.6.*, <a8e3a94711134e898c6021a6b77374efa91b3639, <1720db928e5a58ca7d75ac1d514c3b73fd7061a7, <b713aa0cc344f10f7a9928a230b5f5e780d04078, <=6.18.*, 5.15.212, <0beccbcf50de125be5520d0ffc59af4bb8655482, 6.6.145, 5.10.261, 4.1, <=*, <=5.15.*, 6.12.96, 7.2, <80b5c8779acee0550845394fb3e5176a398aa24c

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.

Gravité et risque d'exploitation

CVE-2026-64452 obtient un score CVSS de 7.1/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.22 %, ce qui la place devant 11.6 % des CVE référencées.

Que faire ?

  • Vérifiez si Linux (versions <=6.1.*, <=6.12.*, <593b78bb3c7ef0c6e9ae6fdf5afa80a5f7573168, 6.18.39, 0, <9c2f5c0829a8c8b904dae36be6d8056b719ac605, <4.1, <cc27aea4d454abfb385ee2c9499c78b96db9b728, <=7.1.*, 7.1.4, 6.1.178, 92aa7c65d295f3cbb96904afe335f683e55584b8, <=5.10.*, <=6.6.*, <a8e3a94711134e898c6021a6b77374efa91b3639, <1720db928e5a58ca7d75ac1d514c3b73fd7061a7, <b713aa0cc344f10f7a9928a230b5f5e780d04078, <=6.18.*, 5.15.212, <0beccbcf50de125be5520d0ffc59af4bb8655482, 6.6.145, 5.10.261, 4.1, <=*, <=5.15.*, 6.12.96, 7.2, <80b5c8779acee0550845394fb3e5176a398aa24c) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références