CVE-2022-49371 Details
Description
In the Linux kernel, the following vulnerability has been resolved: driver core: fix deadlock in __device_attach In __device_attach function, The lock holding logic is as follows: ... __device_attach device_lock(dev) // get lock dev async_schedule_dev(__device_attach_async_helper, dev); // func async_schedule_node async_schedule_node_domain(func) entry = kzalloc(sizeof(struct async_entry), GFP_ATOMIC); /* when fail or work limit, sync to execute func, but __device_attach_async_helper will get lock dev as well, which will lead to A-A deadlock. */ if (!entry || atomic_read(&entry_count) > MAX_WORK) { func; else queue_work_node(node, system_unbound_wq, &entry->work) device_unlock(dev) As shown above, when it is allowed to do async probes, because of out of memory or work limit, async work is not allowed, to do sync execute instead. it will lead to A-A deadlock because of __device_attach_async_helper getting lock dev. To fix the deadlock, move the async_schedule_dev outside device_lock, as we can see, in async_schedule_node_domain, the parameter of queue_work_node is system_unbound_wq, so it can accept concurrent operations. which will also not change the code logic, and will not lead to deadlock.
A deadlock vulnerability has been identified in the Linux kernel's driver core, specifically within the device attachment process. The issue arises in the '__device_attach' function, where the locking mechanism can lead to an 'A-A' deadlock scenario. This occurs when asynchronous probing is allowed, but limitations such as low memory or work capacity prevent the completion of async tasks. As a result, the function attempts to synchronously execute, causing a deadlock as it re-acquires the device lock while another async operation is pending. The vulnerability affects several versions of the Linux kernel.
The vulnerability has been addressed by modifying the locking logic in the '__device_attach' function. The asynchronous scheduling has been moved outside of the device lock, allowing for concurrent operations without disrupting the attachment process. Users should update to the patched version of the Linux kernel where this fix is applied.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Oct 1, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/34fdd9b7def9d2fcb71bb7b0bc4848dd7313767e | kernel.org | Patch |
| https://git.kernel.org/stable/c/36ee9ffca8ef56c302f2855c4a5fccf61c0c1ada | kernel.org | Patch |
| https://git.kernel.org/stable/c/593b595332bd2d65e1a5c1ae7897996c157f5468 | kernel.org | Patch |
| https://git.kernel.org/stable/c/b232b02bf3c205b13a26dcec08e53baddd8e59ed | kernel.org | Patch |
| https://git.kernel.org/stable/c/d53a227bfcd5160ce1b61d9954901968a20651e7 | kernel.org | Patch |
| https://git.kernel.org/stable/c/df6de52b80aa3b46f5ac804412355ffe2e1df93e | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
| CWE-667 | Improper Locking | CISA-ADP |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.2, < 5.4.198 >= 5.5, < 5.10.122 >= 5.11, < 5.15.47 >= 5.16, < 5.17.15 >= 5.18, < 5.18.4 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Oct 1, 2025 | CVE Modified | CISA-ADP |
| Apr 14, 2025 | Initial Analysis | [email protected] |
| Feb 26, 2025 | New CVE Received | kernel.org |