---
id: "CVE-2026-98474"
kind: "vulnerability"
aliases: ["CVE-2026-98474"]
title: "Linux kernel s390 PCI: missing device lock in zpci_report_status"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["ibm-z", "infrastructure", "linux-kernel", "s390"]
not_affected_if: ["non-s390-architecture"]
published_at: "2026-10-18T16:16:57+00:00"
first_seen_at: "2026-10-23T21:57:15+00:00"
updated_at: "2026-10-25T05:25:57+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98474", "first_seen_at": "2026-10-23T21:57:15+00:00"}]
---

# Linux kernel s390 PCI: missing device lock in zpci_report_status

The Linux kernel's s390 PCI code reads a device's driver pointer in zpci_report_status() without holding the device lock, so the state can be inconsistent during recovery. The sources do not state what an attacker gains from this race.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- `uname -r` to see the running kernel version
- unknown whether the s390 PCI path is in use on a given system; the sources do not say

## Fix

- Update the Linux kernel to a release that includes the upstream s390/pci fix for CVE-2026-98474; the fixed version numbers are unknown from the sources

## Timeline

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

## From the sources

In the Linux kernel, the following vulnerability has been resolved:

s390/pci: Fix missing device lock in zpci_report_status()

When pdev is non-NULL, zpci_report_status() accesses the device's driver.
To get a consistent state matching the recovery, the device lock needs to
be held. Do so by expanding the existing device lock critical section.

The lock only needs to be held when the pdev is non-NULL, so extract
the pdev-specific reporting into a helper function which also adds a
lockdep assertion to detect calls without the device lock held.

---

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