7.8
CVE-2024-26934
- EPSS 0.01%
- Published 01.05.2024 06:15:08
- Last modified 21.11.2024 09:03:25
- Source 416baaa9-dc9f-4396-8d5f-8c081f
- CVE-Watchlists
- Open
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>
Data is provided by the National Vulnerability Database (NVD)
Linux ≫ Linux Kernel Version >= 4.4 < 4.19.312
Linux ≫ Linux Kernel Version >= 4.20.0 < 5.4.274
Linux ≫ Linux Kernel Version >= 5.5.0 < 5.10.215
Linux ≫ Linux Kernel Version >= 5.11.0 < 5.15.154
Linux ≫ Linux Kernel Version >= 5.16.0 < 6.1.84
Linux ≫ Linux Kernel Version >= 6.2.0 < 6.6.24
Linux ≫ Linux Kernel Version >= 6.7.0 < 6.7.12
Linux ≫ Linux Kernel Version >= 6.8.0 < 6.8.3
Linux ≫ Linux Kernel Version6.9 Updater1
| Type | Source | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.01% | 0.006 |
| Source | Base Score | Exploit Score | Impact Score | Vector string |
|---|---|---|---|---|
| nvd@nist.gov | 7.8 | 1.8 | 5.9 |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
|
CWE-667 Improper Locking
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.