Skip to main content
← All vulnerabilities
CVE-2026-98930EUVD-2026-108901

KVM: s390: Fix IRQ injection with SIGP Stop and Store Status

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 6.12.112, 6.18.55, 7.2.9
None on Exploit-DB, Metasploit or GitHub

Summary

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

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Linux Linux

    From 6cddd432e3da5e25eccbc13844d03c871674a62e · fixed in 3bd77c59576b1d447fd56cc689ae9523a334b924; From 6cddd432e3da5e25eccbc13844d03c871674a62e · fixed in a379ac504fcb8c6fc2aa36203f5489b9581eb2e0; From 6cddd432e3da5e25eccbc13844d03c871674a62e · fixed in d0e3bf633f0585a0c2c2105ea7723777d764fae5; From 6cddd432e3da5e25eccbc13844d03c871674a62e · fixed in d343407b728a80b74be3c24b59f15e60289ea527

  • Linux Linux

    4.0

  • KernelLinux

    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

References 4

git.kernel.org