{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89578 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89578 is a denial of service vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89578 and fix it if it is affected.\n\nWhat it is: CVE-2026-89578 is a denial of service vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89578 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-89578/ (Markdown: https://insights.sbomify.com/CVE-2026-89578/index.md)","id":"CVE-2026-89578","markdown":"https://insights.sbomify.com/CVE-2026-89578/index.md","name":"CVE-2026-89578","record":{"aliases":["BELL-CVE-2026-89578","DEBIAN-CVE-2026-89578","GHSA-36gx-2j3f-6gcr","UBUNTU-CVE-2026-89578"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A local attacker can cause a system hang in the Linux kernel by triggering a loop in dm-io during misaligned direct I/O operations.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"dm-io: clone the source bio instead of copying its biovec","id":"CVE-2026-89578","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"bpf: Harden bloom filter sizing and indexing on 32-bit kernels","id":"CVE-2026-89579"},"packages":[],"prev":{"headline":"dm-io: report non-retryable errors separatedly","id":"CVE-2026-89577"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker can cause a system hang in the Linux kernel by triggering a loop in dm-io during misaligned direct I/O operations.","url":"https://insights.sbomify.com/CVE-2026-89578/"}