CVE-2026-98930

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 ]

Package Linux Kernel
Published 2026-10-23
Last modified 2026-10-23
Patch available
Yes

Affected versions

Linux kernel versions 4.0 and later are affected. Fixed in 6.12.112, 6.18.55, 7.2.9, 7.3 and their respective stable series.

Affected from
≥ 4.0
Fixed in
✓ 6.12.112 6.12.x ✓ 6.18.55 6.18.x ✓ 7.2.9 7.2.x ✓ 7.3

Frequently asked questions

  • What is CVE-2026-98930?

    CVE-2026-98930 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 4.0 onward and has been patched in 6.12.112, 6.18.55, 7.2.9 and others. CVE-2026-98930 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • Is there a patch available for CVE-2026-98930?

    Yes. CVE-2026-98930 has been patched. Fixed versions include 6.12.112, 6.18.55, 7.2.9 and others. If you are running Linux kernel 4.0 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2026-98930 actively exploited?

    No. CVE-2026-98930 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.