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

Summary

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.

Timeline

1. Sep 11, 2026, 7:44 PM UTCCVE published
2. Oct 19, 2026, 8:49 AM UTCRecord last updated

Affected versions

• Linux Linux

  From 5ff3f74e145adc79b49668adb8de276446acf6be · fixed in 9493ac67623d45b7d4671d2b0b4d0633c2bc2e51; From 5ff3f74e145adc79b49668adb8de276446acf6be · fixed in 8dc48b68d7c3e6ecaae80fc1592befb0e8603d6c; From 5ff3f74e145adc79b49668adb8de276446acf6be · fixed in 62dc37a819a5a5de5cba989ad9e96ee214b9253e

• Linux Linux

  6.18

• KernelLinux

  From 6.18.0 · fixed in 6.18.50; From 6.19.0 · fixed in 7.2.4

References 3