Answer in brief
CVE-2026-43278 records a Unknown severity vulnerability in dm: clear cloned request bio pointer when last clone bio completes. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ab3e1d3bbab9e973aeb4dd4603251578658a47ff <8d9ddad561136f7e6a9346767bf97b4d79e38e67 || >=ab3e1d3bbab9e973aeb4dd4603251578658a47ff <7daf279c674d515fb22a727a7bbc92aeb35c5442 || >=ab3e1d3bbab9e973aeb4dd4603251578658a47ff <e2e738e8dfbbf83bd2bae0467ec4420cc52da42a || >=ab3e1d3bbab9e973aeb4dd4603251578658a47ff <b1c1a2637ebd675aa2d71fee8c70da8791d73850 || >=ab3e1d3bbab9e973aeb4dd4603251578658a47ff <83d72091804600ead96dc9e9f518ea56cb4942f6 || >=ab3e1d3bbab9e973aeb4dd4603251578658a47ff <fb8a6c18fb9a6561f7a15b58b272442b77a242dd | 8d9ddad561136f7e6a9346767bf97b4d79e38e67, 7daf279c674d515fb22a727a7bbc92aeb35c5442, e2e738e8dfbbf83bd2bae0467ec4420cc52da42a, b1c1a2637ebd675aa2d71fee8c70da8791d73850, 83d72091804600ead96dc9e9f518ea56cb4942f6, fb8a6c18fb9a6561f7a15b58b272442b77a242dd |
| Linux/Linuxgeneric | 6.1 | Not reported |
Published upstream
May 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-43278 records a Unknown severity vulnerability in dm: clear cloned request bio pointer when last clone bio completes. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=ab3e1d3bbab9e973aeb4dd4603251578658a47ff <8d9ddad561136f7e6a9346767bf97b4d79e38e67 || >=ab3e1d3bbab9e973aeb4dd4603251578658a47ff <7daf279c674d515fb22a727a7bbc92aeb35c5442 || >=ab3e1d3bbab9e973aeb4dd4603251578658a47ff <e2e738e8dfbbf83bd2bae0467ec4420cc52da42a || >=ab3e1d3bbab9e973aeb4dd4603251578658a47ff <b1c1a2637ebd675aa2d71fee8c70da8791d73850 || >=ab3e1d3bbab9e973aeb4dd4603251578658a47ff <83d72091804600ead96dc9e9f518ea56cb4942f6 || >=ab3e1d3bbab9e973aeb4dd4603251578658a47ff <fb8a6c18fb9a6561f7a15b58b272442b77a242dd | 8d9ddad561136f7e6a9346767bf97b4d79e38e67, 7daf279c674d515fb22a727a7bbc92aeb35c5442, e2e738e8dfbbf83bd2bae0467ec4420cc52da42a, b1c1a2637ebd675aa2d71fee8c70da8791d73850, 83d72091804600ead96dc9e9f518ea56cb4942f6, fb8a6c18fb9a6561f7a15b58b272442b77a242dd |
| Linux/Linuxgeneric | 6.1 | Not reported |
Published upstream
May 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.