nvme-multipath: fix lockdep WARN due to partition scan work
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.1.159, 6.6.118, 6.12, 6.12.60, 6.17.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: nvme-multipath: fix lockdep WARN due to partition scan work Blktests test cases nvme/014, 057 and 058 fail occasionally due to a lockdep WARN. As reported in the Closes tag URL, the WARN indicates that a deadlock can happen due to the dependency among disk->open_mutex, kblockd workqueue completion and partition_scan_work completion. To avoid the lockdep WARN and the potential deadlock, cut the dependency by running the partition_scan_work not by kblockd workqueue but by nvme_wq.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 60de2e03f984cfbcdc12fa552f95087c35a05a98 · fixed in 89456dab7ba5ab63d60945440926673a3205e829; From 4a57f42e5ed42cb8f1beb262c4f6d3e698939e4e · fixed in e2a897ad5f538d314955c747a0a2edb184fcdecd; From 1f021341eef41e77a633186e9be5223de2ce5d48 · fixed in ef4ab2a8abe554379e10303ae86f7c501336ba0d; From 1f021341eef41e77a633186e9be5223de2ce5d48 · fixed in b03eb63288a8ffe3adfb34e68309c8e2edb06d0b; From 1f021341eef41e77a633186e9be5223de2ce5d48 · fixed in 6d87cd5335784351280f82c47cc8a657271929c3; From 6.1.118 · fixed in 6.1.159; From 6.6.62 · fixed in 6.6.118; From 6.11.9 · fixed in 6.12
- Linux Linux
6.12
- KernelLinux
fixed in 6.1.159; From 6.2.0 · fixed in 6.6.118; From 6.7.0 · fixed in 6.12.60; From 6.12.0 · fixed in 6.17.10