md/raid1,raid10: fix deadlock in read error recovery path
- 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.6.160, 6.12.114, 6.18.57, 7.1.5
- 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
Summary
In the Linux kernel, the following vulnerability has been resolved: md/raid1,raid10: fix deadlock in read error recovery path raid1d and raid10d may resubmit a split md cloned bio while handling a read error. In this case, resubmitting the bio can lead to a deadlock if the array is suspended before md_handle_request() acquires an active_io reference via percpu_ref_tryget_live(). Since the cloned bio already holds an active_io reference, trying to acquire another reference via percpu_ref_tryget_live() can lead to a deadlock while the array is suspended. Fix this by using percpu_ref_get() for md cloned bios.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From bb2a9acefaf9ce5bbc1e70f407e34599233d0243 · fixed in 923a6f3172a362d6b2ff12386e376e0e47188f78; From bb2a9acefaf9ce5bbc1e70f407e34599233d0243 · fixed in 0889242775340e2c5b69b1590bd71335dd4fdeda; From bb2a9acefaf9ce5bbc1e70f407e34599233d0243 · fixed in ea2d1d2ebf60b70b602a92261a567d5fc4575eab; From bb2a9acefaf9ce5bbc1e70f407e34599233d0243 · fixed in 38777f014c37972868f1733a651c85288bb8a757; From bb2a9acefaf9ce5bbc1e70f407e34599233d0243 · fixed in 7b15c24f805339a585cfe7d72f446b7e88b9bcc0
- Linux Linux
6.6
- KernelLinux
From 6.6.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.1.5