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-89921KVM: s390: Zero initialize data structures for inject_pfault_token

Description

In the Linux kernel, the following vulnerability has been resolved: KVM: s390: Zero initialize data structures for inject_pfault_token __kvm_inject_pfault_token() only sets .type and .u.ext.ext_params2 of the on-stack struct kvm_s390_irq but the full ext substructure is copied into the cpu local variable on inject. ext_params and pad contain stale stack values. Interrupt delivery only uses ext_params2, so nothing leaks to the guest, but a host user can use the migration ioctls to get to the data. Fix by zero-initializing the irq struct. Do the same for the inti data structure.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 44 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 383d0b050106abecb82f43101cac94fa423af5cd – < 3da26db3323cbccf509005fdbc4ebae842d323cd
    • affected 383d0b050106abecb82f43101cac94fa423af5cd – < 5b0ae4443383fbacd905522f0c95ad6c85a3b43e
    • affected 383d0b050106abecb82f43101cac94fa423af5cd – < 7090818ba774d254eba80979c2d4da23d91de02f
    • affected 383d0b050106abecb82f43101cac94fa423af5cd – < ab1a8a3c9971200938093370da4c67d4427c25f2
    • affected 383d0b050106abecb82f43101cac94fa423af5cd – < b8abc760fa18a389319d977834a30550b3ec18e8
    • affected 383d0b050106abecb82f43101cac94fa423af5cd – < 9b046de62b8098af6e2ba820b125ec9dc5f162c8
    • affected 383d0b050106abecb82f43101cac94fa423af5cd – < 134f235e0e8de54611a72d3cc3f63e5f31246baa
    • affected 383d0b050106abecb82f43101cac94fa423af5cd – < 4e2c7f7cbc27418f9a290399b986c1b85ff93b90
  • Linux · Linux

    • affected 3.19
    • unaffected < 3.19
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .