CVE-2025-68310

PCI error-recovery hang via inverted locking

Published Dec 16, 2025 · Updated Dec 16, 2025

A deadlock in Linux on s390 allows local users to hang PCI error recovery by overlapping mlx5 crash-dump collection. The s390 recovery path takes the PCI configuration-access lock before the devlink lock, while mlx5_crdump_collect takes those locks in the opposite order. Reachability requires privileged control of an mlx5 physical function and concurrent PCI error recovery; the resulting tasks remain blocked and recovery stalls.

CVSS severityUnavailable
Unscored
EPSS probability0.19%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

A deadlock in Linux on s390 allows local users to hang PCI error recovery by overlapping mlx5 crash-dump collection. The s390 recovery path takes the PCI configuration-access lock before the devlink lock, while mlx5_crdump_collect takes those locks in the opposite order. Reachability requires privileged control of an mlx5 physical function and concurrent PCI error recovery; the resulting tasks remain blocked and recovery stalls.

The record

CVE
CVE-2025-68310
Published
Dec 16, 2025
Updated
Dec 16, 2025
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499
Attack vector
local
Privileges
admin

Timeline

How it unfolded

  1. Dec 16, 2025CVE publishedPublication date reported by the CVE source.
  2. Dec 16, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=4cdf2f4e24ff0d345fc36ef6d6aec059333a261e <0fd20f65df6aa430454a0deed8f43efa91c54835
  2. Affected versionversion=4cdf2f4e24ff0d345fc36ef6d6aec059333a261e <3591d56ea9bfd3e7fbbe70f749bdeed689d415f9
  3. Affected versionversion=4cdf2f4e24ff0d345fc36ef6d6aec059333a261e <54f938d9f5693af8ed586a08db4af5d9da1f0f2d
  4. Affected versionversion=4cdf2f4e24ff0d345fc36ef6d6aec059333a261e <b63c061be622b17b495cbf78a6d5f2d4c3147f8e
  5. Affected versionversion=4cdf2f4e24ff0d345fc36ef6d6aec059333a261e <d0df2503bc3c2be385ca2fd96585daad1870c7c5
  6. Affected versionversion=5.16

What conditions does exploitation require?

Attack vectorlocal
Required privilegesadmin

What is affected?

The Linux Kernel Organization · Linuxversion=4cdf2f4e24ff0d345fc36ef6d6aec059333a261e <0fd20f65df6aa430454a0deed8f43efa91c54835; version=4cdf2f4e24ff0d345fc36ef6d6aec059333a261e <3591d56ea9bfd3e7fbbe70f749bdeed689d415f9; version=4cdf2f4e24ff0d345fc36ef6d6aec059333a261e <54f938d9f5693af8ed586a08db4af5d9da1f0f2d; version=4cdf2f4e24ff0d345fc36ef6d6aec059333a261e <b63c061be622b17b495cbf78a6d5f2d4c3147f8e; version=4cdf2f4e24ff0d345fc36ef6d6aec059333a261e <d0df2503bc3c2be385ca2fd96585daad1870c7c5; version=5.16

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesadmin
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo