CVE-2022-49371driver core: fix deadlock in __device_attach
- 5.5MediumCVSS base score
- 0.21%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 15 months later
· 15 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| CISA-ADPADP (enrichment) | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVDNVD · Modified | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (15 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 765230b5f084863183aa8adb3405ab3f32c0b16e – < 593b595332bd2d65e1a5c1ae7897996c157f5468
- affected 765230b5f084863183aa8adb3405ab3f32c0b16e – < 36ee9ffca8ef56c302f2855c4a5fccf61c0c1ada
- affected 765230b5f084863183aa8adb3405ab3f32c0b16e – < df6de52b80aa3b46f5ac804412355ffe2e1df93e
- affected 765230b5f084863183aa8adb3405ab3f32c0b16e – < d53a227bfcd5160ce1b61d9954901968a20651e7
- affected 765230b5f084863183aa8adb3405ab3f32c0b16e – < 34fdd9b7def9d2fcb71bb7b0bc4848dd7313767e
- affected 765230b5f084863183aa8adb3405ab3f32c0b16e – < b232b02bf3c205b13a26dcec08e53baddd8e59ed
- affected 4.2
- unaffected < 4.2
- unaffected 5.4.198 – ≤ 5.4.*
- unaffected 5.10.122 – ≤ 5.10.*
- unaffected 5.15.47 – ≤ 5.15.*
- unaffected 5.17.15 – ≤ 5.17.*
- unaffected 5.18.4 – ≤ 5.18.*
- unaffected 5.19 – ≤ *
References
References6
- https://git.kernel.org/stable/c/593b595332bd2d65e1a5c1ae7897996c157f5468 (opens in a new tab)
- https://git.kernel.org/stable/c/36ee9ffca8ef56c302f2855c4a5fccf61c0c1ada (opens in a new tab)
- https://git.kernel.org/stable/c/df6de52b80aa3b46f5ac804412355ffe2e1df93e (opens in a new tab)
- https://git.kernel.org/stable/c/d53a227bfcd5160ce1b61d9954901968a20651e7 (opens in a new tab)
- https://git.kernel.org/stable/c/34fdd9b7def9d2fcb71bb7b0bc4848dd7313767e (opens in a new tab)
- https://git.kernel.org/stable/c/b232b02bf3c205b13a26dcec08e53baddd8e59ed (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2022-54858 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2022-49371)Record last updated .