Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

HighCVSS 7.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.11% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 7daf279c674d515fb22a727a7bbc92aeb35c5442, 83d72091804600ead96dc9e9f518ea56cb4942f6, 8d9ddad561136f7e6a9346767bf97b4d79e38e67.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 7daf279c674d515fb22a727a7bbc92aeb35c5442, 83d72091804600ead96dc9e9f518ea56cb4942f6, 8d9ddad561136f7e6a9346767bf97b4d79e38e67 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
May 6, 2026
Updated
Nov 11, 2026
EPSS
0.1% · 1th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-43278

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.1affected
    • ab3e1d3bbab9e973aeb4dd4603251578658a47ff and later · before 8d9ddad561136f7e6a9346767bf97b4d79e38e67affected · git
    • ab3e1d3bbab9e973aeb4dd4603251578658a47ff and later · before 7daf279c674d515fb22a727a7bbc92aeb35c5442affected · git
    • ab3e1d3bbab9e973aeb4dd4603251578658a47ff and later · before e2e738e8dfbbf83bd2bae0467ec4420cc52da42aaffected · git
    • ab3e1d3bbab9e973aeb4dd4603251578658a47ff and later · before b1c1a2637ebd675aa2d71fee8c70da8791d73850affected · git
    • ab3e1d3bbab9e973aeb4dd4603251578658a47ff and later · before 83d72091804600ead96dc9e9f518ea56cb4942f6affected · git
    • ab3e1d3bbab9e973aeb4dd4603251578658a47ff and later · before fb8a6c18fb9a6561f7a15b58b272442b77a242ddaffected · git
    • before 6.1not affected · semver
    • 6.1.165 and later · up to and including 6.1.*not affected · semver
    • 6.6.128 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.170-16.1.170-1
Debian:13linuxbefore 6.12.85-16.12.85-1
Debian:14linuxbefore 6.19.6-16.19.6-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-43276May 6, 2026 · net: mana: Fix double destroy_workqueue on service rescan PCI path
    31Monitor
  • ← EarlierCVE-2026-43277May 6, 2026 · APEI/GHES: ensure that won't go past CPER allocated record
    22Monitor
  • Later →CVE-2026-43279May 6, 2026 · ALSA: usb-audio: Add sanity check for OOB writes at silencing
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux7daf279c674d515fb22a727a7bbc92aeb35c5442Vendor (CNA)
Linux Linux83d72091804600ead96dc9e9f518ea56cb4942f6Vendor (CNA)
Linux Linux8d9ddad561136f7e6a9346767bf97b4d79e38e67Vendor (CNA)
Linux Linuxb1c1a2637ebd675aa2d71fee8c70da8791d73850Vendor (CNA)
Linux Linuxe2e738e8dfbbf83bd2bae0467ec4420cc52da42aVendor (CNA)
Linux Linuxfb8a6c18fb9a6561f7a15b58b272442b77a242ddVendor (CNA)
debian:linux6.1.170-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-434142 days apartscsi: qla2xxx: Completely fix fcport double free
    39Monitor
  • CVE-2026-430115 days apartnet/x25: Fix potential double free of skb
    39Monitor
  • CVE-2026-3160812 days apartsmb: server: avoid double-free in smb_direct_free_sendmsg after smb_direct_flush_send_list()
    39Monitor
  • CVE-2026-3160912 days apartsmb: client: avoid double-free in smbd_free_send_io() after smbd_send_batch_flush()
    39Monitor
  • CVE-2026-5299349 days aparttipc: fix double-free in tipc_buf_append()
    39Monitor
  • CVE-2026-6388874 days apartscsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd()
    39Monitor

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-415 · Double Free

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records