CVE-2026-43278

HIGH EPSS 1.9%
Published May 6, 20261mo ago · Modified Jun 17, 20261w ago
7.8 CVSS 3.1
High
Find Similar
Published May 6, 2026 1mo ago
Last Modified Jun 17, 2026 1w ago

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.

CVSS Details

Base Score
7.8
Exploitability
1.8
Impact
5.9
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality High
Integrity High
Availability High

Threat Intelligence

EPSS Exploit Probability
1.9% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Weaknesses 1

CWE-415

Affected Products 5

VendorProductVersionRange
linuxlinux_kernel*≥6.1  –  <6.1.165
linuxlinux_kernel*≥6.2  –  <6.6.128
linuxlinux_kernel*≥6.7  –  <6.12.75
linuxlinux_kernel*≥6.13  –  <6.18.16
linuxlinux_kernel*≥6.19  –  <6.19.6

References 8

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

Remediation

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