{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89921 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89921 is a 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-89921 and fix it if it is affected.\n\nWhat it is: CVE-2026-89921 is a 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-89921 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-89921/ (Markdown: https://insights.sbomify.com/CVE-2026-89921/index.md)","id":"CVE-2026-89921","markdown":"https://insights.sbomify.com/CVE-2026-89921/index.md","name":"CVE-2026-89921","record":{"aliases":["AZL-101535","BELL-CVE-2026-89921","DEBIAN-CVE-2026-89921","GHSA-fm87-69w9-6w3j","UBUNTU-CVE-2026-89921"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel KVM","requires_auth":"low_privilege","summary":"A local attacker with KVM access can read uninitialized kernel stack memory via migration ioctls due to missing zero-initialization in s390 fault injection.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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: Zero initialize data structures for inject_pfault_token\n\n__kvm_inject_pfault_token() only sets .type and .u.ext.ext_params2 of\nthe on-stack struct kvm_s390_irq but the full ext substructure is copied\ninto the cpu local variable on inject. ext_params and pad contain stale\nstack values.\n\nInterrupt delivery only uses ext_params2, so nothing leaks to the guest,\nbut a host user can use the migration ioctls to get to the data.\n\nFix by zero-initializing the irq struct.\nDo the same for the inti data structure.","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: Zero initialize data structures for inject_pfault_token","id":"CVE-2026-89921","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"KVM: s390: Take srcu when importing watchpoint data","id":"CVE-2026-89922"},"packages":[],"prev":{"headline":"KVM: s390: Fix memory corruption by not reinjecting CK machine checks","id":"CVE-2026-89920"},"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 local attacker with KVM access can read uninitialized kernel stack memory via migration ioctls due to missing zero-initialization in s390 fault injection.","url":"https://insights.sbomify.com/CVE-2026-89921/"}