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.
Affected products
linux: linux kernel
References8
- git.kernel.org/stable/c/2a52d55c86a429dac47886b8424e67f90b001e67 Patch
- git.kernel.org/stable/c/3ad5fbcced4e9c2b0fee3c1b76289a147fc35b89 Patch
- git.kernel.org/stable/c/5ec61fbef9ec5635c492ae63dfb5d13f2bdf1023 Patch
- git.kernel.org/stable/c/6c82f88bc7a8458d5c60f9b354c4d32d233f0cac Patch
- git.kernel.org/stable/c/8f50613bff228272577893aa10a346a2f3063e49 Patch
- git.kernel.org/stable/c/abf76d3239dee97b66e7241ad04811f1ce562e28 Patch
- git.kernel.org/stable/c/f3e409476ad0703c54c14f245e4e143c8124e1bd Patch
- git.kernel.org/stable/c/fe7a0f4be283b40dd592540027279735120d0d6f Patch
Metrics
- CVSS 3.1
-
7.8
HIGH
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 0% percentile: 3 · as of 13 November 2026
- CWE
- CWE-416
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.