{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89573 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89573 is a high-severity memory corruption 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-89573 and fix it if it is affected.\n\nWhat it is: CVE-2026-89573 is a high-severity memory corruption 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-89573 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-89573/ (Markdown: https://insights.sbomify.com/CVE-2026-89573/index.md)","id":"CVE-2026-89573","markdown":"https://insights.sbomify.com/CVE-2026-89573/index.md","name":"CVE-2026-89573","record":{"aliases":["AZL-100521","BELL-CVE-2026-89573","DEBIAN-CVE-2026-89573","GHSA-pg3h-8qxx-35hj","UBUNTU-CVE-2026-89573"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel dm-cache","requires_auth":"low_privilege","summary":"A flaw in the Linux kernel dm-cache allows attackers to cause memory corruption via crafted metadata, potentially leading to code execution or privilege escalation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndm array: reject an array block whose value size is not the caller's\n\narray_block_check() can only compare the header against itself, so a block\nwith value_size 4 and max_entries 1018 is internally consistent and passes.\ndm-cache keeps two arrays -- mappings at 8 bytes and hints at 4 -- and the\nroots for both live in the superblock. Point the mappings root at a hint\nblock and __load_mappings() walks it through an info whose value size is 8,\nso element_at() strides 8 bytes over 4-byte entries and reaches offset 8160\nof a 4096-byte block.\n\nget_ablock() and __shadow_ablock() are the two places that hold the block\nand the caller at once. Reject there when the two value sizes disagree.\nArrays only ever read their own blocks, so this fires on crafted metadata\nonly.","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 array: reject an array block whose value size is not the caller's","id":"CVE-2026-89573","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"dm array: validate array block headers on read","id":"CVE-2026-89574"},"packages":[],"prev":{"headline":"cpufreq: apple-soc: Fix OPP table cleanup","id":"CVE-2026-89572"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A flaw in the Linux kernel dm-cache allows attackers to cause memory corruption via crafted metadata, potentially leading to code execution or privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-89573/"}