CVE-2026-64455
Vulnérabilité non évaluée dans Linux (Linux)
Description
In the Linux kernel, the following vulnerability has been resolved: USB: chaoskey: Fix slab-use-after-free in chaoskey_release() The chaoskey driver has a use-after-free bug in its release routine. If the user closes the device file after the USB device has been unplugged, a debugging log statement will try to access the usb_interface structure after it has been deallocated: BUG: KASAN: slab-use-after-free in dev_driver_string (drivers/base/core.c:2406) Read of size 8 at addr ffff888168e8a0b8 by task chaoskey_raw_re/10106 Hardware name: QEMU Ubuntu 24.04 PC v2 (i440FX + PIIX, arch_caps fix, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 Call Trace: <TASK> dump_stack_lvl (lib/dump_stack.c:94 lib/dump_stack.c:120) print_report (mm/kasan/report.c:378 mm/kasan/report.c:482) kasan_report (mm/kasan/report.c:595) dev_driver_string (drivers/base/core.c:2406) __dynamic_dev_dbg (lib/dynamic_debug.c:906) chaoskey_release (drivers/usb/misc/chaoskey.c:323) __fput (fs/file_table.c:510) fput_close_sync (fs/file_table.c:615) __x64_sys_close (fs/open.c:1507 fs/open.c:1492 fs/open.c:1492) do_syscall_64 (arch/x86/entry/syscall_64.c:63 arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) The driver's last reference to the interface structure is dropped in the chaoskey_free() routine, so the code must not use the interface -- even in a debugging statement -- after that routine returns. (Exception: If we know that another reference is held by someone else, such as the device core while the disconnect routine runs, there's no problem. Thanks to Johan Hovold for pointing this out.) Since the bad access is part of an unimportant debugging statement, we can fix the problem simply by removing the whole statement.
Gravité et risque d'exploitation
CVE-2026-64455 obtient un score CVSS de 0.0/10, soit une gravité non évaluée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.18 %, ce qui la place devant 7.5 % des CVE référencées.
Que faire ?
- Vérifiez si Linux (versions <=6.1.*, <abf76d3239dee97b66e7241ad04811f1ce562e28, <=6.12.*, 6.18.39, 0, <4.1, <=7.1.*, 7.1.4, <6c82f88bc7a8458d5c60f9b354c4d32d233f0cac, 6.1.178, <=5.10.*, <=6.6.*, <5ec61fbef9ec5635c492ae63dfb5d13f2bdf1023, <fe7a0f4be283b40dd592540027279735120d0d6f, <=6.18.*, <f3e409476ad0703c54c14f245e4e143c8124e1bd, 5.15.212, 6.6.145, 5.10.261, <3ad5fbcced4e9c2b0fee3c1b76289a147fc35b89, <8f50613bff228272577893aa10a346a2f3063e49, 4.1, <=*, <=5.15.*, <2a52d55c86a429dac47886b8424e67f90b001e67, 6.12.96, 7.2, 66e3e591891da9899a8990792da080432531ffd4) 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
- https://git.kernel.org/stable/c/fe7a0f4be283b40dd592540027279735120d0d6f
- https://git.kernel.org/stable/c/5ec61fbef9ec5635c492ae63dfb5d13f2bdf1023
- https://git.kernel.org/stable/c/f3e409476ad0703c54c14f245e4e143c8124e1bd
- https://git.kernel.org/stable/c/6c82f88bc7a8458d5c60f9b354c4d32d233f0cac
- https://git.kernel.org/stable/c/3ad5fbcced4e9c2b0fee3c1b76289a147fc35b89
- https://git.kernel.org/stable/c/2a52d55c86a429dac47886b8424e67f90b001e67
- https://git.kernel.org/stable/c/8f50613bff228272577893aa10a346a2f3063e49
- https://git.kernel.org/stable/c/abf76d3239dee97b66e7241ad04811f1ce562e28
