CVE-2026-89578
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.
Leer descripción completaMostrar menos
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.
CVSS
NVD no ha asignado puntuación CVSS a esta CVE (habitual desde el cambio de política de abril de 2026).
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.21%
- Percentil entre todas las CVEs puntuadas: 10
- Fecha de la puntuación: 6/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
Tecnologías afectadas (1)
⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.
Referencias
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-89578",
"cveTags": [],
"metrics": {},
"affected": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"affectedData": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "5ff3f74e145adc79b49668adb8de276446acf6be",
"lessThan": "9493ac67623d45b7d4671d2b0b4d0633c2bc2e51",
"versionType": "git"
},
{
"status": "affected",
"version": "5ff3f74e145adc79b49668adb8de276446acf6be",
"lessThan": "8dc48b68d7c3e6ecaae80fc1592befb0e8603d6c",
"versionType": "git"
},
{
"status": "affected",
"version": "5ff3f74e145adc79b49668adb8de276446acf6be",
"lessThan": "62dc37a819a5a5de5cba989ad9e96ee214b9253e",
"versionType": "git"
}
],
"programFiles": [
"drivers/md/dm-io.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "6.18"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.18",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.18.50",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.2.4",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"drivers/md/dm-io.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-09-11T20:19:42.000",
"references": [
{
"url": "https://git.kernel.org/stable/c/62dc37a819a5a5de5cba989ad9e96ee214b9253e",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/8dc48b68d7c3e6ecaae80fc1592befb0e8603d6c",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/9493ac67623d45b7d4671d2b0b4d0633c2bc2e51",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndm-io: clone the source bio instead of copying its biovec\n\nFor DM_IO_BIO requests, do_region() built each destination bio by walking\nthe source bio's biovec and re-adding the pages one at a time, tracking\nthe remaining transfer in sectors. The vector lengths are byte granular\nand need not be sector aligned (e.g. a misaligned O_DIRECT buffer split\nacross pages), so the sector-based accounting could lose a sub-sector\nfragment: to_sector() truncated the remainder and the outer loop spun\nforever submitting empty bios, hanging the I/O.\n\nThere is no need to rebuild the biovec at all. The destination reads into\n(or writes from) exactly the same pages as the source bio, so the bio can\nsimply clone the source's biovec with bio_alloc_clone() and remap it to\nthe target device. The clone inherits the source's iterator and alignment,\nand the block layer splits it to the target's limits on submission, so the\nwhole region maps to a single cloned bio with no manual page copying or\nsector accounting.\n\nThis removes the per-page copy path (and its open-coded bvec dpages\nhelpers) for bio-backed I/O and fixes the hang on misaligned direct I/O to\na dm-mirror device. Page-list, vma and kmem sources keep the existing copy\npath."
}
],
"lastModified": "2026-09-11T20:19:42.000",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}