VDB

CVE-2026-89578

CVE-2026-89578 PUBLISHED

dm-io: clone the source bio instead of copying its biovec

Reported by linux · Published September 11, 2026

In the Linux kernel, the following vulnerability has been resolved: dm-io: clone the source bio instead of copying its biovec For DM_IO_BIO requests, do_region() built each destination bio by walking the source bio's biovec and re-adding the pages one at a time, tracking the remaining transfer in sectors. The vector lengths are byte granular and need not be sector aligned (e.g. a misaligned O_DIRECT buffer split across pages), so the sector-based accounting could lose a sub-sector fragment: to_sector() truncated the remainder and the outer loop spun forever submitting empty bios, hanging the I/O. There is no need to rebuild the biovec at all. The destination reads into (or writes from) exactly the same pages as the source bio, so the bio can simply clone the source's biovec with bio_alloc_clone() and remap it to the target device. The clone inherits the source's iterator and alignment, and the block layer splits it to the target's limits on submission, so the whole region maps to a single cloned bio with no manual page copying or sector accounting. This removes the per-page copy path (and its open-coded bvec dpages helpers) for bio-backed I/O and fixes the hang on misaligned direct I/O to a dm-mirror device. Page-list, vma and kmem sources keep the existing copy path.

EPSS 0.20% · 9.5th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel6.18-develAmazon Linux1:6.18.51-120.162.amzn2023
kernel6.18-tools-develAmazon Linux1:6.18.51-120.162.amzn2023
bpftool6.18Amazon Linux1:6.18.51-120.162.amzn2023
perf6.18Amazon Linux1:6.18.51-120.162.amzn2023
python3-perf6.18Amazon Linux1:6.18.51-120.162.amzn2023
kernel-livepatch-6.18.51-120.162Amazon Linux1:1.0-0.amzn2023
microvm-kernel6.18Amazon Linux1:6.18.51-120.162.amzn2023
LinuxLinux9493ac67623d45b7d4671d2b0b4d0633c2bc2e51, 8dc48b68d7c3e6ecaae80fc1592befb0e8603d6c, 6.18

Risk scores

EPSS Score
0.20%
9.5th percentile

Affected products

VendorProductVersions
LinuxLinux5ff3f74e145adc79b49668adb8de276446acf6be, 5ff3f74e145adc79b49668adb8de276446acf6be, 5ff3f74e145adc79b49668adb8de276446acf6be
LinuxLinux6.18, 0, 6.18.50
amazon:2023kernel6.18-devel0
amazon:2023kernel6.18-tools-devel0
amazon:2023bpftool6.180
amazon:2023perf6.180
amazon:2023python3-perf6.180
amazon:2023kernel-livepatch-6.18.51-120.1620
amazon:2023microvm-kernel6.180
LinuxLinux7.3, 7.2.4, 6.18.50
amazon:2023kernel6.18-modules-extra0
linuxlinux_kernel6.18, 6.18, 6.18
amazon:2023kernel6.18-headers0
amazon:2023kernel6.18-modules-extra-common0
amazon:2023kernel6.180
amazon:2023kernel6.18-tools0

Timeline

  • Sep 11, 2026 CVE Published
  • Sep 12, 2026 EPSS Score (11 in total, the first dated here)
  • Oct 19, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2026-89578
vulnetix vdb fixes CVE-2026-89578

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-89578/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›