Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 14 days later

    Published

  3. · 40 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-80921, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Received3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.8.

Affected products

  • Linux · Linux

    • affected 6b79de4b056e5a2febc0c61233d8f0ad7868e49c – < d110b3297f11ef227098b8a82ade2d5f123b7d2f
    • affected 6b79de4b056e5a2febc0c61233d8f0ad7868e49c – < 59d51550b5cb916bda037673a721a404b3b47a0d
    • affected 6b79de4b056e5a2febc0c61233d8f0ad7868e49c – < f6079dca67eccb5eabef9f72437948c66dc5131f
    • affected 6b79de4b056e5a2febc0c61233d8f0ad7868e49c – < 087c19cc60a8caa1a08e1e434c8be2caf6c27733
    • affected 6b79de4b056e5a2febc0c61233d8f0ad7868e49c – < 7d23489f51109e3ebba5b5db8c5f0185af7b7fdf
    • affected 6b79de4b056e5a2febc0c61233d8f0ad7868e49c – < 935eeba276012916c76243e5cbb843efd8fdb75d
    • affected 6b79de4b056e5a2febc0c61233d8f0ad7868e49c – < d4bcd2df6d0d2af916b4fe1a533958778ea7c45b
    • affected 6b79de4b056e5a2febc0c61233d8f0ad7868e49c – < 29b4f7bc2991313bd3e6f6fb8fdf1b173f086dd6
    • affected 6b79de4b056e5a2febc0c61233d8f0ad7868e49c – < 34d5b5b646c91cfb9338d7a12c955a70ffb8c66b
  • Linux · Linux

    • affected 4.20
    • unaffected < 4.20
    • unaffected 5.10.269 – ≤ 5.10.*
    • unaffected 5.15.220 – ≤ 5.15.*
    • unaffected 6.1.187 – ≤ 6.1.*
    • unaffected 6.6.156 – ≤ 6.6.*
    • unaffected 6.12.108 – ≤ 6.12.*
    • unaffected 6.18.49 – ≤ 6.18.*
    • unaffected 7.1.13 – ≤ 7.1.*
    • unaffected 7.2.3 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80921 badge
[![CVE-2026-80921](https://cveledger.app/badge/CVE-2026-80921.svg)](https://cveledger.app/cve/CVE-2026-80921)

Record last updated .