Skip to content
Heist/ feed
Back to feed
HighFix available

dm: clear cloned request bio pointer when last clone bio completes

Type: advisorySources: OSV

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.

Products
Kernel
Affected versions
Not specified
Fixed versions
6.1.165, 6.12.75, 6.18.16, 6.19.6, 6.6.128
CVEs
CVE-2026-43278
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 14:38 UTC · Revision 1

Source evidence

dm: clear cloned request bio pointer when last clone bio completes

core-osv · Original source

Published 6 May 2026, 11:29 UTC

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.

osv:CVE-2026-43278

Kernel

Fixed versions: 6.1.165, 6.6.128, 6.12.75, 6.18.16, 6.19.6

Complete source record
{
  "id": "c4aab79ff86daf964c352e37c85f93d812b663773e6aaec796cffff3b220fe40",
  "url": "https://osv.dev/vulnerability/CVE-2026-43278",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "dm: clear cloned request bio pointer when last clone bio completes",
    "summary": "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.",
    "evidence": "osv:CVE-2026-43278",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.1.165",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.6.128",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.12.75",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.18.16",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "6.19.6",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "CVE-2026-43278",
      "aliases": [
        "CVE-2026-43278"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "ab3e1d3bbab9e973aeb4dd4603251578658a47ff"
                },
                {
                  "fixed": "8d9ddad561136f7e6a9346767bf97b4d79e38e67"
                },
                {
                  "fixed": "7daf279c674d515fb22a727a7bbc92aeb35c5442"
                },
                {
                  "fixed": "e2e738e8dfbbf83bd2bae0467ec4420cc52da42a"
                },
                {
                  "fixed": "b1c1a2637ebd675aa2d71fee8c70da8791d73850"
                },
                {
                  "fixed": "83d72091804600ead96dc9e9f518ea56cb4942f6"
                },
                {
                  "fixed": "fb8a6c18fb9a6561f7a15b58b272442b77a242dd"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-43278.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.1.0"
                },
                {
                  "fixed": "6.1.165"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.2.0"
                },
                {
                  "fixed": "6.6.128"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.7.0"
                },
                {
                  "fixed": "6.12.75"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.13.0"
                },
                {
                  "fixed": "6.18.16"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "6.19.6"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-43278.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:29.580358195Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/7daf279c674d515fb22a727a7bbc92aeb35c5442",
        "https://git.kernel.org/stable/c/83d72091804600ead96dc9e9f518ea56cb4942f6",
        "https://git.kernel.org/stable/c/8d9ddad561136f7e6a9346767bf97b4d79e38e67",
        "https://git.kernel.org/stable/c/b1c1a2637ebd675aa2d71fee8c70da8791d73850",
        "https://git.kernel.org/stable/c/e2e738e8dfbbf83bd2bae0467ec4420cc52da42a",
        "https://git.kernel.org/stable/c/fb8a6c18fb9a6561f7a15b58b272442b77a242dd",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/43xxx/CVE-2026-43278.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-43278",
        "https://git.kernel.org/stable/c/3d746b639be4b4f5cd8ce2b06aa52dc443f50edc",
        "https://git.kernel.org/stable/c/9a95b98202113045bc1a5bcb30388a500f25e050",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/43xxx/CVE-2026-43278.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-43278",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 496444,
  "published_at": "2026-05-06T11:29:00.193+00:00"
}