{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80921 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80921 is a high-severity vulnerability in Linux, published on 9 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-80921 and fix it if it is affected.\n\nWhat it is: CVE-2026-80921 is a high-severity vulnerability in Linux, published on 9 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-80921 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-80921/ (Markdown: https://insights.sbomify.com/CVE-2026-80921/index.md)","id":"CVE-2026-80921","markdown":"https://insights.sbomify.com/CVE-2026-80921/index.md","name":"CVE-2026-80921","record":{"aliases":["AZL-99950","BELL-CVE-2026-80921","DEBIAN-CVE-2026-80921","GHSA-337q-m32v-p95j","UBUNTU-CVE-2026-80921"],"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 nested guest on s390x KVM can access stale crypto bits, potentially reading data from unavailable devices due to improper memory zeroing.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: s390: vsie: zero stale crypto bits\n\nWhen shadowing crypto access bits from a format0 apcb (crycb 0 or 1),\nthe bits 64..255 are unchanged from whatever is in the vsie page in the\ncrycb and thus in the apcb. This gives a nested guest potential access\nto a device no longer available. Zero out the remaining bits.","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: vsie: zero stale crypto bits","id":"CVE-2026-80921","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":9,"next":{"headline":"crypto: qcom-rng - Allow zero as a random number","id":"CVE-2026-80922"},"packages":[],"prev":{"headline":"io_uring: defer eventfd signaling when queued from a wakeup handler","id":"CVE-2026-80920"},"products":["Linux"],"published":"2026-09-09","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A nested guest on s390x KVM can access stale crypto bits, potentially reading data from unavailable devices due to improper memory zeroing.","url":"https://insights.sbomify.com/CVE-2026-80921/"}