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… (CVE-2026-89578)
A vulnerability in the Linux kernel's device mapper I/O (dm-io) subsystem was resolved by changing the handling of bio vectors. The issue involved the dm-io code rebuilding destination bios by copying the source bio's biovec with sector-based accounting that could lose sub-sector fragments, causing an infinite loop and I/O hang on misaligned direct I/O to dm-mirror devices. The fix clones the source bio's biovec instead of copying it, eliminating the problematic per-page copy path and preventing the hang.
AI Analysis
Technical Summary
The Linux kernel dm-io subsystem had a flaw in handling DM_IO_BIO requests where do_region() rebuilt destination bios by iterating over the source bio's biovec and re-adding pages with sector-based accounting. Because vector lengths are byte granular and not necessarily sector aligned, the sector accounting truncated sub-sector fragments, causing the loop to spin indefinitely submitting empty bios and hanging I/O. The fix replaces this approach by cloning the source bio's biovec using bio_alloc_clone(), which preserves the iterator and alignment, allowing the block layer to handle splitting. This removes the per-page copy path and fixes the hang on misaligned direct I/O to dm-mirror devices.
Potential Impact
The vulnerability could cause I/O operations to hang indefinitely when performing misaligned direct I/O to dm-mirror devices, leading to potential denial of service conditions on affected systems. There is no indication of data corruption or privilege escalation from the provided information.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to clone the source bio's biovec instead of copying it, resolving the infinite loop and I/O hang issue. Users should update to the fixed kernel version once available. Patch status is not yet confirmed in the provided data; check the official Linux kernel advisories or vendor updates for the current remediation guidance.
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… (CVE-2026-89578)
Description
A vulnerability in the Linux kernel's device mapper I/O (dm-io) subsystem was resolved by changing the handling of bio vectors. The issue involved the dm-io code rebuilding destination bios by copying the source bio's biovec with sector-based accounting that could lose sub-sector fragments, causing an infinite loop and I/O hang on misaligned direct I/O to dm-mirror devices. The fix clones the source bio's biovec instead of copying it, eliminating the problematic per-page copy path and preventing the hang.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel dm-io subsystem had a flaw in handling DM_IO_BIO requests where do_region() rebuilt destination bios by iterating over the source bio's biovec and re-adding pages with sector-based accounting. Because vector lengths are byte granular and not necessarily sector aligned, the sector accounting truncated sub-sector fragments, causing the loop to spin indefinitely submitting empty bios and hanging I/O. The fix replaces this approach by cloning the source bio's biovec using bio_alloc_clone(), which preserves the iterator and alignment, allowing the block layer to handle splitting. This removes the per-page copy path and fixes the hang on misaligned direct I/O to dm-mirror devices.
Potential Impact
The vulnerability could cause I/O operations to hang indefinitely when performing misaligned direct I/O to dm-mirror devices, leading to potential denial of service conditions on affected systems. There is no indication of data corruption or privilege escalation from the provided information.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to clone the source bio's biovec instead of copying it, resolving the infinite loop and I/O hang issue. Users should update to the fixed kernel version once available. Patch status is not yet confirmed in the provided data; check the official Linux kernel advisories or vendor updates for the current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-36gx-2j3f-6gcr
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-89578"]
Threat ID: 6aa4a01155bf5e2cf5a866b3
Added to database: 09/12/2026, 00:42:57 UTC
Last enriched: 09/12/2026, 01:07:29 UTC
Last updated: 09/12/2026, 01:07:29 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.