CVE-2026-45907

Local system hang via reversed mlx5e locks

Published May 27, 2026 · Updated May 27, 2026

Improper locking in Linux Kernel 6.16 through 6.18.13 and 6.19 through 6.19.3 allows local users to hang affected systems. The mlx5e TX, RX, and PTP health-reporter work handlers take a netdev instance lock before devlink_health_report takes the devlink lock, reversing initialization order and deadlocking recovery. Reachability requires an mlx5e device and a TX error, RX timeout, PTP queue fault, or TX timeout that invokes the affected recovery path; the reported consequence is loss of availability.

CVSS severity5.5
Medium
EPSS probability0.12%
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

Improper locking in Linux Kernel 6.16 through 6.18.13 and 6.19 through 6.19.3 allows local users to hang affected systems. The mlx5e TX, RX, and PTP health-reporter work handlers take a netdev instance lock before devlink_health_report takes the devlink lock, reversing initialization order and deadlocking recovery. Reachability requires an mlx5e device and a TX error, RX timeout, PTP queue fault, or TX timeout that invokes the affected recovery path; the reported consequence is loss of availability.

The record

CVE
CVE-2026-45907
Published
May 27, 2026
Updated
May 27, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
CWE-667, CAPEC-25, T1499.004
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. May 27, 2026CVE publishedPublication date reported by the CVE source.
  2. May 27, 2026Record 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=6.16
  2. Affected versionversion=8f7b00307bf14676b7e7f0210110a36aa0ff3e93 <4329514c61abefe4961541b128c549b017bab5ad
  3. Affected versionversion=8f7b00307bf14676b7e7f0210110a36aa0ff3e93 <63f9d5fb4d8040077df801ca3270e2f02d55e0d9
  4. Affected versionversion=8f7b00307bf14676b7e7f0210110a36aa0ff3e93 <83ac0304a2d77519dae1e54c9713cbe1aedf19c9

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=6.16; version=8f7b00307bf14676b7e7f0210110a36aa0ff3e93 <4329514c61abefe4961541b128c549b017bab5ad; version=8f7b00307bf14676b7e7f0210110a36aa0ff3e93 <63f9d5fb4d8040077df801ca3270e2f02d55e0d9; version=8f7b00307bf14676b7e7f0210110a36aa0ff3e93 <83ac0304a2d77519dae1e54c9713cbe1aedf19c9

Published CVSS scores

5.5NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-667Improper Locking
CAPEC-25Forced Deadlock
T1499.004Endpoint Denial of Service: Application or System Exploitation

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