dm: clear cloned request bio pointer when last clone bio completes
- 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.165, 6.6.128, 6.12.75, 6.18.16, 6.19.6
- 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: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: dm: clear cloned request bio pointer when last clone bio completes Stale rq->bio values have been observed to cause double-initialization of cloned bios in request-based device-mapper targets, leading to use-after-free and double-free scenarios. One such case occurs when using dm-multipath on top of a PCIe NVMe namespace, where cloned request bios are freed during blk_complete_request(), but rq->bio is left intact. Subsequent clone teardown then attempts to free the same bios again via blk_rq_unprep_clone(). The resulting double-free path looks like: nvme_pci_complete_batch() nvme_complete_batch() blk_mq_end_request_batch() blk_complete_request() // called on a DM clone request bio_endio() // first free of all clone bios ... rq->end_io() // end_clone_request() dm_complete_request(tio->orig) dm_softirq_done() dm_done() dm_end_request() blk_rq_unprep_clone() // second free of clone bios Fix this by clearing the clone request's bio pointer when the last cloned bio completes, ensuring that later teardown paths do not attempt to free already-released bios.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From ab3e1d3bbab9e973aeb4dd4603251578658a47ff · fixed in 8d9ddad561136f7e6a9346767bf97b4d79e38e67; From ab3e1d3bbab9e973aeb4dd4603251578658a47ff · fixed in 7daf279c674d515fb22a727a7bbc92aeb35c5442; From ab3e1d3bbab9e973aeb4dd4603251578658a47ff · fixed in e2e738e8dfbbf83bd2bae0467ec4420cc52da42a; From ab3e1d3bbab9e973aeb4dd4603251578658a47ff · fixed in b1c1a2637ebd675aa2d71fee8c70da8791d73850; From ab3e1d3bbab9e973aeb4dd4603251578658a47ff · fixed in 83d72091804600ead96dc9e9f518ea56cb4942f6; From ab3e1d3bbab9e973aeb4dd4603251578658a47ff · fixed in fb8a6c18fb9a6561f7a15b58b272442b77a242dd
- Linux Linux
6.1
- KernelLinux
From 6.1.0 · fixed in 6.1.165; From 6.2.0 · fixed in 6.6.128; From 6.7.0 · fixed in 6.12.75; From 6.13.0 · fixed in 6.18.16; From 6.19.0 · fixed in 6.19.6