CVE-2024-26934
Last modified
CVE-2024-26934 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix deadlock in usb_deauthorize_interface() Among the attribute file callback routines in drivers/usb/core/sysfs.c, the interface_authorized_store() function is the only one which acquires a device lock on an ancestor device: It calls usb_deauthorize_interface(), which locks the interface's parent USB device. The will lead to deadlock if another process already owns that lock and tries to remove the interface, whether through a configuration change or because the device has been disconnected. As part of the removal procedure, device_del() waits for all ongoing sysfs attribute callbacks to complete. EPSS estimates a 0.19% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix deadlock in usb_deauthorize_interface() Among the attribute file callback routines in drivers/usb/core/sysfs.c, the interface_authorized_store() function is the only one which acquires a device lock on an ancestor device: It calls usb_deauthorize_interface(), which locks the interface's parent USB device. The will lead to deadlock if another process already owns that lock and tries to remove the interface, whether through a configuration change or because the device has been disconnected. As part of the removal procedure, device_del() waits for all ongoing sysfs attribute callbacks to complete. But usb_deauthorize_interface() can't complete until the device lock has been released, and the lock won't be released until the removal has finished. The mechanism provided by sysfs to prevent this kind of deadlock is to use the sysfs_break_active_protection() function, which tells sysfs not to wait for the attribute callback. Reported-and-tested by: Yue Sun <samsun1006219@gmail.com> Reported by: xingwei lee <xrivendell7@gmail.com>
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 4.4, < 4.19.312 | — |
| Linux | Linux Kernel | >= 4.20.0, < 5.4.274 | — |
| Linux | Linux Kernel | >= 5.5.0, < 5.10.215 | — |
| Linux | Linux Kernel | >= 5.11.0, < 5.15.154 | — |
| Linux | Linux Kernel | >= 5.16.0, < 6.1.84 | — |
| Linux | Linux Kernel | >= 6.2.0, < 6.6.24 | — |
| Linux | Linux Kernel | >= 6.7.0, < 6.7.12 | — |
| Linux | Linux Kernel | >= 6.8.0, < 6.8.3 | — |
| Linux | Linux Kernel | 6.9 | R1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-26934?
How severe is CVE-2024-26934?
How do I fix CVE-2024-26934?
Are you affected by CVE-2024-26934?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
