CVE 7.8 HIGH

dm: clear cloned request bio pointer when last clone bio completes_CVE-2026-43278

7.8 / 10
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Description

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.

Basic Information

ID CVE-2026-43278
Source Linux
Published May 6, 2026 at 11:29
Modified May 8, 2026 at 12:41

Affected Product

Vendor Linux
Product Linux
Version ab3e1d3bbab9e973aeb4dd4603251578658a47ff
Affected Versions Linux Linux ab3e1d3bbab9e973aeb4dd4603251578658a47ff
Linux Linux ab3e1d3bbab9e973aeb4dd4603251578658a47ff
Linux Linux ab3e1d3bbab9e973aeb4dd4603251578658a47ff
Linux Linux ab3e1d3bbab9e973aeb4dd4603251578658a47ff
Linux Linux ab3e1d3bbab9e973aeb4dd4603251578658a47ff
Linux Linux ab3e1d3bbab9e973aeb4dd4603251578658a47ff
Linux Linux 6.1

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.