Live › vulnerability › CVE-2026-98652
Go to dashboardThe Linux kernel's KVM on IBM s390 did not hold the kvm->srcu lock while performing a store status operation in kvm_s390_set_irq_state(), a locking gap that can leave memory accessed without proper protection. The fix takes kvm->srcu in that function; the sources give no further impact detail.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Only hosts running the Linux kernel KVM hypervisor on IBM s390 (mainframe) hardware are relevant. Systems on other architectures are not affected by this s390-specific change.
No product ranges from the sources yet.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
KVM: s390: Add missing srcu in kvm_s390_set_irq_state()
Like kvm_s390_inject_vcpu(), kvm_s390_set_irq_state() also needs the kvm->srcu or the slots lock when performing the Store status operation.
Fix by taking kvm->srcu in kvm_s390_set_irq_state().
This page as .md · .json · in your agent: get_signal("CVE-2026-98652")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.