Kernel memory corruption via stale firmware completion
Published Jun 19, 2024 · Updated Aug 5, 2026
A use-after-free in the Linux kernel mlx5 command interface allows local users to corrupt kernel memory during an internal device error. In drivers/net/ethernet/mellanox/mlx5/core/cmd.c, mlx5_cmd_comp_handler processes a firmware completion after mlx5_cmd_flush has released the command entry, causing a second reference drop and stale-pointer access. Reachability requires an mlx5 PCI device, low-privileged local access, an internal-error transition, and a completion in the narrow flush window; outcomes include kernel data exposure, arbitrary writes, and a panic.
Summary
What happened
A use-after-free in the Linux kernel mlx5 command interface allows local users to corrupt kernel memory during an internal device error. In drivers/net/ethernet/mellanox/mlx5/core/cmd.c, mlx5_cmd_comp_handler processes a firmware completion after mlx5_cmd_flush has released the command entry, causing a second reference drop and stale-pointer access. Reachability requires an mlx5 PCI device, low-privileged local access, an internal-error transition, and a completion in the narrow flush window; outcomes include kernel data exposure, arbitrary writes, and a panic.
The record
- CVE
- CVE-2024-38555
- Published
- Jun 19, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 19, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
- Affected versionversion=27c79b3a9212cf4ba634c157e07d29548181a208 <f6fbb8535e990f844371086ab2c1221f71f993d3
- Affected versionversion=2e5d24b3bf091802c5456dc8f8f6a6be4493c8ca
- Affected versionversion=5.10.20 <5.10.219
- Affected versionversion=5.11.3 <5.12
- Affected versionversion=5.12
- Affected versionversion=51d138c2610a236c1ed0059d034ee4c74f452b86 <1337ec94bc5a9eed250e33f5f5c89a28a6bfabdb
- Affected versionversion=51d138c2610a236c1ed0059d034ee4c74f452b86 <1d5dce5e92a70274de67a59e1e674c3267f94cd7
- Affected versionversion=51d138c2610a236c1ed0059d034ee4c74f452b86 <3cb92b0ad73d3f1734e812054e698d655e9581b0
- Affected versionversion=51d138c2610a236c1ed0059d034ee4c74f452b86 <7ac4c69c34240c6de820492c0a28a0bd1494265a
- Affected versionversion=51d138c2610a236c1ed0059d034ee4c74f452b86 <bf8aaf0ae01c27ae3c06aa8610caf91e50393396
- Affected versionversion=51d138c2610a236c1ed0059d034ee4c74f452b86 <db9b31aa9bc56ff0d15b78f7e827d61c4a096e40
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.
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