CVE-2022-49371
published 2025-02-26CVE-2022-49371: In the Linux kernel, the following vulnerability has been resolved: driver core: fix deadlock in __device_attach In __device_attach function, The lock holding…
PriorityP420medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.21%
11.8th percentile
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.
Affected
17 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.18.5-1 (bookworm) | linux 5.18.5-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 765230b5f084863183aa8adb3405ab3f32c0b16e < 593b595332bd2d65e1a5c1ae7897996c157f5468 | 593b595332bd2d65e1a5c1ae7897996c157f5468 |
| linux | linux | >= 765230b5f084863183aa8adb3405ab3f32c0b16e < 36ee9ffca8ef56c302f2855c4a5fccf61c0c1ada | 36ee9ffca8ef56c302f2855c4a5fccf61c0c1ada |
| linux | linux | >= 765230b5f084863183aa8adb3405ab3f32c0b16e < df6de52b80aa3b46f5ac804412355ffe2e1df93e | df6de52b80aa3b46f5ac804412355ffe2e1df93e |
| linux | linux | >= 765230b5f084863183aa8adb3405ab3f32c0b16e < d53a227bfcd5160ce1b61d9954901968a20651e7 | d53a227bfcd5160ce1b61d9954901968a20651e7 |
| linux | linux | >= 765230b5f084863183aa8adb3405ab3f32c0b16e < 34fdd9b7def9d2fcb71bb7b0bc4848dd7313767e | 34fdd9b7def9d2fcb71bb7b0bc4848dd7313767e |
| linux | linux | >= 765230b5f084863183aa8adb3405ab3f32c0b16e < b232b02bf3c205b13a26dcec08e53baddd8e59ed | b232b02bf3c205b13a26dcec08e53baddd8e59ed |
| linux | linux_kernel | >= 0 < 5.10.127-1 | 5.10.127-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 0 < 5.18.5-1 | 5.18.5-1 |
| linux | linux_kernel | >= 4.2 < 5.4.198 | 5.4.198 |
| linux | linux_kernel | >= 5.11 < 5.15.47 | 5.15.47 |
| linux | linux_kernel | >= 5.16 < 5.17.15 | 5.17.15 |
| linux | linux_kernel | >= 5.18 < 5.18.4 | 5.18.4 |
| linux | linux_kernel | >= 5.5 < 5.10.122 | 5.10.122 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: driver core: fix deadlock in __device_attach
vendor_redhat·2025-02-26·CVSS 5.5
CVE-2022-49371 [MEDIUM] CWE-667 kernel: driver core: fix deadlock in __device_attach
kernel: driver core: fix deadlock in __device_attach
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,
Debian
CVE-2022-49371: linux - In the Linux kernel, the following vulnerability has been resolved: driver core...
vendor_debian·2022·CVSS 5.5
CVE-2022-49371 [MEDIUM] CVE-2022-49371: linux - In the Linux kernel, the following vulnerability has been resolved: driver core...
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
GHSA
GHSA-r45q-6fx6-2q7q: In the Linux kernel, the following vulnerability has been resolved:
driver core: fix deadlock in __device_attach
In __device_attach function, The lo
ghsa_unreviewed·2025-04-14
CVE-2022-49371 [MEDIUM] CWE-667 GHSA-r45q-6fx6-2q7q: In the Linux kernel, the following vulnerability has been resolved:
driver core: fix deadlock in __device_attach
In __device_attach function, The lo
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
OSV
CVE-2022-49371: In the Linux kernel, the following vulnerability has been resolved: driver core: fix deadlock in __device_attach In __device_attach function, The lock
osv·2025-02-26·CVSS 5.5
CVE-2022-49371 [MEDIUM] CVE-2022-49371: In the Linux kernel, the following vulnerability has been resolved: driver core: fix deadlock in __device_attach In __device_attach function, The lock
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
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/34fdd9b7def9d2fcb71bb7b0bc4848dd7313767ehttps://git.kernel.org/stable/c/36ee9ffca8ef56c302f2855c4a5fccf61c0c1adahttps://git.kernel.org/stable/c/593b595332bd2d65e1a5c1ae7897996c157f5468https://git.kernel.org/stable/c/b232b02bf3c205b13a26dcec08e53baddd8e59edhttps://git.kernel.org/stable/c/d53a227bfcd5160ce1b61d9954901968a20651e7https://git.kernel.org/stable/c/df6de52b80aa3b46f5ac804412355ffe2e1df93e
2025-02-26
Published