{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89645 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89645 is a 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-89645 and fix it if it is affected.\n\nWhat it is: CVE-2026-89645 is a 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-89645 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-89645/ (Markdown: https://insights.sbomify.com/CVE-2026-89645/index.md)","id":"CVE-2026-89645","markdown":"https://insights.sbomify.com/CVE-2026-89645/index.md","name":"CVE-2026-89645","record":{"aliases":["AZL-100844","BELL-CVE-2026-89645","DEBIAN-CVE-2026-89645","GHSA-m8pq-6746-5gfc","UBUNTU-CVE-2026-89645"],"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 reference counting error in the Linux kernel's Btrfs filesystem can cause memory leaks and potential instability during relocation recovery failures.","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\nbtrfs: drop recovered reloc root refs on recovery failure\n\nDuring relocation recovery, each fs root gets a reference to its relocation\nroot. If loading or adding a later root fails, or if the first transaction\ncommit fails, btrfs_recover_relocation() jumps to out_unset before\nmerge_reloc_roots() and clean_dirty_subvols().\n\nput_reloc_control() drops the list-owned relocation root references, but it\ndoes not clear fs_root-\u003ereloc_root or drop the references owned by those\npointers. Mount cleanup only drops them when BTRFS_FS_ERROR is set, so an\nerror such as -ENOMEM while processing a later root can leave references\nbehind.\n\nKeep temporary references to the fs roots associated during recovery. On\nfailure, clear their reloc_root pointers and drop the corresponding\nreferences. Once the first transaction commit succeeds, drop only the\ntemporary fs root references and let the normal merge and cleanup paths\nhandle the relocation roots.\n\nFault injection on a pending-relocation image confirmed the cleanup gap.\nWith an injected first-commit failure, 25 fs roots had reloc_root set with\nfs_error=0. With this fix, the same failure path drops that count to 0\nbefore mount fails.","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":"btrfs: drop recovered reloc root refs on recovery failure","id":"CVE-2026-89645","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":"ceph: fix leaked inode reference on writeback abort at umount","id":"CVE-2026-89646"},"packages":[],"prev":{"headline":"btrfs: fix extent map leak in NOCOW direct I/O write","id":"CVE-2026-89644"},"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-21","vendors":["Linux"]},"summary":"A reference counting error in the Linux kernel's Btrfs filesystem can cause memory leaks and potential instability during relocation recovery failures.","url":"https://insights.sbomify.com/CVE-2026-89645/"}