Vulnary
← back to the feed
Critical· 9.8official fix available

CVE-2025-39726

The Linux kernel's s390/ism driver fails to enforce that only one request‑response sequence can occur per ISM function at a time, allowing concurrent commands to overwrite each other and potentially cause device errors, DMA issues, or lost/executed‑twice commands. This flaw is rated critical with a CVSS base score of 9.8. A patch has been released to serialize command processing and fix the concurrency issue.

publishedSep 5, 2025
last modifiedJul 30, 2026
sourcesNVD
severity · cvss
9.8
critical · how bad it is
exploitation · epss
<1%
13th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 29, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Linux kernel versions that lack the s390/ism concurrency fix (e.g., the 6.16 series referenced in the CPE data).

02

Real-world impact

Attackers could trigger the race condition to corrupt ISM function state, leading to connection breakdowns, invalid DMA events (PEC 2/3A), and possible denial of service or unintended command execution.

03

Why this severity

CVSS 3.1 metrics show Attack Vector: Network, Attack Complexity: Low, Privileges Required: None, User Interaction: None, Scope: Unchanged, with High impacts to Confidentiality, Integrity, and Availability, yielding a base score of 9.8 (Critical).

04

What to do about it

official fix available
recommended steps
  1. 01Obtain the latest Linux kernel update from your distribution that includes the s390/ism concurrency management fix.
  2. 02Install the kernel update according to your distribution's standard procedure.
  3. 03Reboot the system to load the patched kernel.

NVD-referenced vendor advisory (the NVD description states the vulnerability has been resolved in the Linux kernel).

05

Timeline

  1. Sep 5, 2025 · Sep 5, 2025
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 30, 2026 · 6d ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 30, 2026 · 6d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →