System crash via unlocked flow-state check
Published Oct 4, 2025 · Updated Oct 4, 2025
Race condition in the Linux kernel mlx5e traffic-control path allows local users to crash the system during concurrent flow removal. The mlx5e deletion path checks the NOT_READY flag before taking uplink_priv->unready_flows_lock, allowing a workqueue and caller to remove the same unready_flows entry twice. Reachability requires local access and an active mlx5e traffic-control flow; the demonstrated consequence is a kernel crash, with no reported data disclosure or modification.
Summary
What happened
Race condition in the Linux kernel mlx5e traffic-control path allows local users to crash the system during concurrent flow removal. The mlx5e deletion path checks the NOT_READY flag before taking uplink_priv->unready_flows_lock, allowing a workqueue and caller to remove the same unready_flows entry twice. Reachability requires local access and an active mlx5e traffic-control flow; the demonstrated consequence is a kernel crash, with no reported data disclosure or modification.
The record
- CVE
- CVE-2023-53581
- Published
- Oct 4, 2025
- Updated
- Oct 4, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 2025CVE publishedPublication date reported by the CVE source.
- Oct 4, 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.
- Affected versionversion=5.4
- Affected versionversion=ad86755b18d5edf1956f6d25c844f27289216877 <30c281a77fb1b2d362030ea243dd663201d62a21
- Affected versionversion=ad86755b18d5edf1956f6d25c844f27289216877 <65e64640e97c0f223e77f9ea69b5a46186b93470
- Affected versionversion=ad86755b18d5edf1956f6d25c844f27289216877 <82ac62d76a000871004f534ad294e763e966d3b0
- Affected versionversion=ad86755b18d5edf1956f6d25c844f27289216877 <e962fd5933ebc767ce2a1cf7b7c85035b5a5d04c
- Affected versionversion=ad86755b18d5edf1956f6d25c844f27289216877 <f7ceedd1d124217a67ed1a67bbd7a7b1288705e3
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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