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


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** AZL-110711, BELL-CVE-2026-98930, DEBIAN-CVE-2026-98930, GHSA-hqr4-mv6v-vc35, UBUNTU-CVE-2026-98930

## What is CVE-2026-98930?

CVE-2026-98930 is a vulnerability in Linux, published on 23 Oct 2026. 

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

## Which versions are affected by CVE-2026-98930?


## How do I fix CVE-2026-98930?

Upgrade to a fixed version.

## Is CVE-2026-98930 being exploited?

There is no known exploitation of CVE-2026-98930 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98930 and fix it if it is affected.

What it is: CVE-2026-98930 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98930 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98930/ (Markdown: https://insights.sbomify.com/CVE-2026-98930/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98930
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98930
- OSV: https://osv.dev/vulnerability/CVE-2026-98930

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98930/
Summaries are generated and may contain mistakes; the official description above is the record.