{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89962 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89962 is a memory corruption vulnerability in Linux, published on 16 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-89962 and fix it if it is affected.\n\nWhat it is: CVE-2026-89962 is a memory corruption vulnerability in Linux, published on 16 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-89962 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-89962/ (Markdown: https://insights.sbomify.com/CVE-2026-89962/index.md)","id":"CVE-2026-89962","markdown":"https://insights.sbomify.com/CVE-2026-89962/index.md","name":"CVE-2026-89962","record":{"aliases":["AZL-101387","BELL-CVE-2026-89962","DEBIAN-CVE-2026-89962","GHSA-52p7-4c9h-jcc7","UBUNTU-CVE-2026-89962"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_modify","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"high_privilege","summary":"A logic error in Linux kernel kexec memory range merging can cause valid memory fragments to be lost, potentially allowing a crash kernel to overwrite active memory.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\npowerpc/kexec_file: Prevent kexec range truncation\n\nSashiko AI review pointed out the following issue.\n\nThe __merge_memory_ranges() function incorrectly handles overlapping\nmemory ranges when merging them. Although sort_memory_ranges() sorts all\nranges by their start address in ascending order beforehand, the merge\nlogic remains defective in two ways:\n\n1. It compares the current range's start against the previous element (i-1)\n   instead of the running target index (idx)\n\n2. It unconditionally overwrites 'ranges[idx].end' with 'ranges[i].end'.\n\nThis logic flaw leads to critical memory truncation when a larger memory\nrange completely subsumes subsequent smaller ranges.\n\nFor example, consider a sorted input array with three ranges:\n  Range A (idx=0): [0x1000 - 0x9000]\n  Range B (i=1):   [0x2000 - 0x5000] (completely inside Range A)\n  Range C (i=2):   [0x6000 - 0x8000] (completely inside Range A)\n\n1. When i=1 (Range B):\n   ranges[1].start (0x2000) \u003c= ranges[0].end + 1 (0x9001) is TRUE.\n   The code executes: ranges[0].end = ranges[1].end, which erroneously\n   shrinks Range A's end from 0x9000 down to 0x5000.\n\n2. When i=2 (Range C):\n   ranges[2].start (0x6000) \u003c= ranges[1].end + 1 (0x5001) is FALSE.\n   The code falls into the else block, creating a broken new range.\n\nAs a result, valid memory fragments [0x5001 - 0x5fff] and [0x8001 - 0x9000]\nare completely lost from the kexec exclude lists, potentially allowing\nthe crash kernel to overwrite active memory, causing data corruption\nor crashes.\n\nFix this by ensuring the start of the current range is compared against the\nend of the active merged range (idx), and use max() to safely prevent the\nouter boundary from being truncated.","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":"powerpc/kexec_file: Prevent kexec range truncation","id":"CVE-2026-89962","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"powerpc/kexec_file: Fix null-ptr-def in extra size calculation","id":"CVE-2026-89963"},"packages":[],"prev":{"headline":"powerpc/mm: fix wrong addr_pfn tracking in compound vmemmap population","id":"CVE-2026-89961"},"products":["Linux"],"published":"2026-09-16","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-21","vendors":["Linux"]},"summary":"A logic error in Linux kernel kexec memory range merging can cause valid memory fragments to be lost, potentially allowing a crash kernel to overwrite active memory.","url":"https://insights.sbomify.com/CVE-2026-89962/"}