Bug 2531066 (CVE-2026-80921) - CVE-2026-80921 kernel: KVM: s390: vsie: zero stale crypto bits
Summary: CVE-2026-80921 kernel: KVM: s390: vsie: zero stale crypto bits
Keywords:
Status: NEW
Alias: CVE-2026-80921
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-09 16:41 UTC by OSIDB Bzimport
Modified: 2026-10-07 20:28 UTC (History)
17 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2026:75746 0 None None None 2026-10-05 10:48:58 UTC
Red Hat Product Errata RHSA-2026:75747 0 None None None 2026-10-05 11:24:03 UTC
Red Hat Product Errata RHSA-2026:76738 0 None None None 2026-10-07 20:28:53 UTC

Description OSIDB Bzimport 2026-09-09 16:41:14 UTC
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.

Comment 5 Jon Orris 2026-10-05 10:48:56 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:75746 https://access.redhat.com/errata/RHSA-2026:75746

Comment 6 Jon Orris 2026-10-05 11:24:02 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 8

Via RHSA-2026:75747 https://access.redhat.com/errata/RHSA-2026:75747

Comment 7 Jon Orris 2026-10-07 20:28:51 UTC
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 10

Via RHSA-2026:76738 https://access.redhat.com/errata/RHSA-2026:76738


Note You need to log in before you can comment on or make changes to this bug.