CVE-2026-98930KVM: s390: Fix IRQ injection with SIGP Stop and Store Status
- —Not scoredno CVSS score yet
- 0.19%Exploitation in 30 daysEPSS · top 91% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: KVM: s390: Fix IRQ injection with SIGP Stop and Store Status When __inject_sigp_stop() is called for a Stop and Store Status operation, if the vCPU is running, the interrupt is marked as pending and the status is stored by the thread performing the KVM_RUN IOCTL. If the vCPU is already stopped, the status is stored immediately. Storing the status means writing into userspace, which might fault, and __inject_sigp_stop() is called from do_inject_vcpu() which in turn is always called holding a spinlock, which is obviously an issue. Fix this by returning -EWOULDBLOCK from __inject_sigp_stop(), and adding a bool flag to indicate whether a store status is needed. The callers of do_inject_vcpu() are modified to pass the pointer to the bool flag; whenever a Store Status operation is needed, the callers can now perform it outside the spinlock. Opportunistically refactor kvm_s390_set_irq_state() to use scoped_guard() and __free(). [ Added Fixes tag while picking -- Claudio ]
Timeline
ID reserved
By Linux
- 28 days later
· 28 days later
Published
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.19% · top 91% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 6cddd432e3da5e25eccbc13844d03c871674a62e – < 3bd77c59576b1d447fd56cc689ae9523a334b924
- affected 6cddd432e3da5e25eccbc13844d03c871674a62e – < a379ac504fcb8c6fc2aa36203f5489b9581eb2e0
- affected 6cddd432e3da5e25eccbc13844d03c871674a62e – < d0e3bf633f0585a0c2c2105ea7723777d764fae5
- affected 6cddd432e3da5e25eccbc13844d03c871674a62e – < d343407b728a80b74be3c24b59f15e60289ea527
- affected 4.0
- unaffected < 4.0
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.55 – ≤ 6.18.*
- unaffected 7.2.9 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References4
- https://git.kernel.org/stable/c/3bd77c59576b1d447fd56cc689ae9523a334b924 (opens in a new tab)
- https://git.kernel.org/stable/c/a379ac504fcb8c6fc2aa36203f5489b9581eb2e0 (opens in a new tab)
- https://git.kernel.org/stable/c/d0e3bf633f0585a0c2c2105ea7723777d764fae5 (opens in a new tab)
- https://git.kernel.org/stable/c/d343407b728a80b74be3c24b59f15e60289ea527 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-108901 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98930)Record last updated .