---
id: "CVE-2026-98652"
kind: "vulnerability"
aliases: ["CVE-2026-98652"]
title: "Linux kernel KVM s390: missing SRCU lock in IRQ state setting"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["infrastructure", "kvm", "linux-kernel", "mainframe", "s390"]
not_affected_if: ["non-s390-architecture"]
published_at: "2026-10-18T16:17:18+00:00"
first_seen_at: "2026-10-23T21:57:16+00:00"
updated_at: "2026-10-25T05:19:38+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98652", "first_seen_at": "2026-10-23T21:57:16+00:00"}]
---

# Linux kernel KVM s390: missing SRCU lock in IRQ state setting

The 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, check and fix written by a model from the sources; labelled as such._

## Fix

- Update the Linux kernel to a release that includes the upstream commit adding kvm->srcu to kvm_s390_set_irq_state() (version unknown from sources)

## Timeline

- 2026-10-23T21:57:16+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-98652

## From the sources

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().

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_