CVE-2026-98930

Unknown

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 ]

SeverityUnknown
CVSS—
Exploit probability—
ProductLinux
PublishedOct 23, 2026
First seenOct 23, 2026

How to fix

Update
  • Linux Linux3bd77c59576b1d447fd56cc689ae9523a334b924, a379ac504fcb8c6fc2aa36203f5489b9581eb2e0, d0e3bf633f0585a0c2c2105ea7723777d764fae5, d343407b728a80b74be3c24b59f15e60289ea527 or later

Affected products

ProductAffected versionsFixed in
Linux Linux6cddd432e3da5e25eccbc13844d03c871674a62e ≤ v < 3bd77c59576b1d447fd56cc689ae9523a334b924, 6cddd432e3da5e25eccbc13844d03c871674a62e ≤ v < a379ac504fcb8c6fc2aa36203f5489b9581eb2e0, 6cddd432e3da5e25eccbc13844d03c871674a62e ≤ v < d0e3bf633f0585a0c2c2105ea7723777d764fae5, 6cddd432e3da5e25eccbc13844d03c871674a62e ≤ v < d343407b728a80b74be3c24b59f15e60289ea527, 4.03bd77c59576b1d447fd56cc689ae9523a334b924, a379ac504fcb8c6fc2aa36203f5489b9581eb2e0, d0e3bf633f0585a0c2c2105ea7723777d764fae5, d343407b728a80b74be3c24b59f15e60289ea527

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.