High 7.8Published May 6, 2026

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

Updated under an hour ago (Oct 28, 2026, 1:10 AM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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.

CVSS: 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE): CWE-415
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Modified
Record last updated: Oct 19, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from ab3e1d3bbab9e973aeb4dd4603251578658a47ff before 8d9ddad561136f7e6a9346767bf97b4d79e38e67; from ab3e1d3bbab9e973aeb4dd4603251578658a47ff before 7daf279c674d515fb22a727a7bbc92aeb35c5442; from ab3e1d3bbab9e973aeb4dd4603251578658a47ff before e2e738e8dfbbf83bd2bae0467ec4420cc52da42a; from ab3e1d3bbab9e973aeb4dd4603251578658a47ff before b1c1a2637ebd675aa2d71fee8c70da8791d73850; from ab3e1d3bbab9e973aeb4dd4603251578658a47ff before 83d72091804600ead96dc9e9f518ea56cb4942f6; from ab3e1d3bbab9e973aeb4dd4603251578658a47ff before fb8a6c18fb9a6561f7a15b58b272442b77a242dd	CNA record
linux linux_kernel linux:linux_kernel	from 6.1 before 6.1.165; from 6.2 before 6.6.128; from 6.7 before 6.12.75; from 6.13 before 6.18.16; from 6.19 before 6.19.6	NVD

References

References

https://git.kernel.org/stable/c/8d9ddad561136f7e6a9346767bf97b4d79e38e67	patch
https://git.kernel.org/stable/c/7daf279c674d515fb22a727a7bbc92aeb35c5442	patch
https://git.kernel.org/stable/c/e2e738e8dfbbf83bd2bae0467ec4420cc52da42a	patch
https://git.kernel.org/stable/c/b1c1a2637ebd675aa2d71fee8c70da8791d73850	patch
https://git.kernel.org/stable/c/83d72091804600ead96dc9e9f518ea56cb4942f6	patch
https://git.kernel.org/stable/c/fb8a6c18fb9a6561f7a15b58b272442b77a242dd	patch
https://git.kernel.org/stable/c/3d746b639be4b4f5cd8ce2b06aa52dc443f50edc	patch
https://git.kernel.org/stable/c/9a95b98202113045bc1a5bcb30388a500f25e050	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.