{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89923 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89923 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-89923 and fix it if it is affected.\n\nWhat it is: CVE-2026-89923 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-89923 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-89923/ (Markdown: https://insights.sbomify.com/CVE-2026-89923/index.md)","id":"CVE-2026-89923","markdown":"https://insights.sbomify.com/CVE-2026-89923/index.md","name":"CVE-2026-89923","record":{"aliases":["AZL-101465","BELL-CVE-2026-89923","DEBIAN-CVE-2026-89923","GHSA-69xh-7r26-q3mw","UBUNTU-CVE-2026-89923"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel KVM","requires_auth":"low_privilege","summary":"A memory leak in the Linux kernel's KVM s390 implementation allows local attackers to exhaust system memory by repeatedly creating and destroying virtual CPUs with active hardware breakpoints.","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\nKVM: s390: Free guest debug data on vcpu destroy\n\nkvm_s390_clear_bp_data() is only called from\nkvm_arch_vcpu_ioctl_set_guest_debug(), i.e. when user space changes or\ndisables debugging. A vCPU that is destroyed while hardware breakpoints\nare still armed - the normal case when the VMM just exits or crashes -\nleaks hw_bp_info, hw_wp_info and all old_data buffers, since generic KVM\nfrees the vCPU right after kvm_arch_vcpu_destroy().\n\nThat is bounded by MAX_BP_COUNT entries, so roughly 8 KiB per vCPU, but\nit is unbounded over VM lifetimes. The allocations are\nGFP_KERNEL_ACCOUNT, so the charge also outlives the exiting process and\npins dying memcgs.\n\nFix by clearing the debug data on vCPU destruction. Calling it\nunconditionally is fine: struct kvm_vcpu is zero allocated, so for a vCPU\nthat never enabled debugging the counters are 0 and the pointers NULL.","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":"KVM: s390: Free guest debug data on vcpu destroy","id":"CVE-2026-89923","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":"KVM: s390: Fix old_data leak in guest debug error path","id":"CVE-2026-89924"},"packages":[],"prev":{"headline":"KVM: s390: Take srcu when importing watchpoint data","id":"CVE-2026-89922"},"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-19","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel's KVM s390 implementation allows local attackers to exhaust system memory by repeatedly creating and destroying virtual CPUs with active hardware breakpoints.","url":"https://insights.sbomify.com/CVE-2026-89923/"}