CVE-2026-98930: Linux kernel · KVM: s390: Fix IRQ injection with SIGP Stop and Store Status
Source GCVE Database
Not known to be exploited · fixed in d343407b728a80b74be3c24b59f15e60289ea527 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 17:16 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in d343407b728a80b74be3c24b59f15e60289ea527, d0e3bf633f0585a0c2c2105ea7723777d764fae5, a379ac504fcb8c6fc2aa36203f5489b9581eb2e0 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 23 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to d343407b728a80b74be3c24b59f15e60289ea527, d0e3bf633f0585a0c2c2105ea7723777d764fae5, a379ac504fcb8c6fc2aa36203f5489b9581eb2e0 or 3bd77c59576b1d447fd56cc689ae9523a334b924.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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 ]
References
- nvd.nist.gov/vuln/detail/CVE-2026-98930 (opens in a new tab)
- git.kernel.org/stable/c/3bd77c59576b1d447fd56cc689ae9523a334b924 (opens in a new tab)
- git.kernel.org/stable/c/a379ac504fcb8c6fc2aa36203f5489b9581eb2e0 (opens in a new tab)
- git.kernel.org/stable/c/d0e3bf633f0585a0c2c2105ea7723777d764fae5 (opens in a new tab)
- git.kernel.org/stable/c/d343407b728a80b74be3c24b59f15e60289ea527 (opens in a new tab)