CVE-2026-43278dm: clear cloned request bio pointer when last clone bio completes
- 7.8HighCVSS base score
- 0.12%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 5 days later
· 5 days later
Published
- 6 months later
· 6 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Modified | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected ab3e1d3bbab9e973aeb4dd4603251578658a47ff – < 8d9ddad561136f7e6a9346767bf97b4d79e38e67
- affected ab3e1d3bbab9e973aeb4dd4603251578658a47ff – < 7daf279c674d515fb22a727a7bbc92aeb35c5442
- affected ab3e1d3bbab9e973aeb4dd4603251578658a47ff – < e2e738e8dfbbf83bd2bae0467ec4420cc52da42a
- affected ab3e1d3bbab9e973aeb4dd4603251578658a47ff – < b1c1a2637ebd675aa2d71fee8c70da8791d73850
- affected ab3e1d3bbab9e973aeb4dd4603251578658a47ff – < 83d72091804600ead96dc9e9f518ea56cb4942f6
- affected ab3e1d3bbab9e973aeb4dd4603251578658a47ff – < fb8a6c18fb9a6561f7a15b58b272442b77a242dd
- affected 6.1
- unaffected < 6.1
- unaffected 6.1.165 – ≤ 6.1.*
- unaffected 6.6.128 – ≤ 6.6.*
- unaffected 6.12.75 – ≤ 6.12.*
- unaffected 6.18.16 – ≤ 6.18.*
- unaffected 6.19.6 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References6
- https://git.kernel.org/stable/c/8d9ddad561136f7e6a9346767bf97b4d79e38e67 (opens in a new tab)
- https://git.kernel.org/stable/c/7daf279c674d515fb22a727a7bbc92aeb35c5442 (opens in a new tab)
- https://git.kernel.org/stable/c/e2e738e8dfbbf83bd2bae0467ec4420cc52da42a (opens in a new tab)
- https://git.kernel.org/stable/c/b1c1a2637ebd675aa2d71fee8c70da8791d73850 (opens in a new tab)
- https://git.kernel.org/stable/c/83d72091804600ead96dc9e9f518ea56cb4942f6 (opens in a new tab)
- https://git.kernel.org/stable/c/fb8a6c18fb9a6561f7a15b58b272442b77a242dd (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-27674 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-43278)Record last updated .