Local kernel memory corruption via unlocked recovery
Published Sep 11, 2024 · Updated Aug 5, 2026
Improper locking in the Linux mlx5e driver allows local users to corrupt kernel memory during transmit-timeout recovery. The tx-timeout reporter calls mlx5e_safe_reopen_channels without holding state_lock, allowing concurrent channel teardown and statistics work to access inconsistent or freed channel state. Exploitation requires a local low-privileged account and an active mlx5e interface; the resulting race can disclose or corrupt kernel memory, interrupt the network device, or crash the host.
Summary
What happened
Improper locking in the Linux mlx5e driver allows local users to corrupt kernel memory during transmit-timeout recovery. The tx-timeout reporter calls mlx5e_safe_reopen_channels without holding state_lock, allowing concurrent channel teardown and statistics work to access inconsistent or freed channel state. Exploitation requires a local low-privileged account and an active mlx5e interface; the resulting race can disclose or corrupt kernel memory, interrupt the network device, or crash the host.
The record
- CVE
- CVE-2024-45019
- Published
- Sep 11, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 11, 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=514232495aa523641febaa58b687fe6df1cd0b73 <03d3734bd692affe4d0e9c9d638f491aaf37411b
- Affected versionversion=6.1.69 <6.1.107
- Affected versionversion=6.6.8 <6.6.48
- Affected versionversion=6.7
- Affected versionversion=8ce3d969348a7c7fa3469588eb1319f9f3cc0eaa <b3b9a87adee97854bcd71057901d46943076267e
- Affected versionversion=eab0da38912ebdad922ed0388209f7eb0a5163cd <8e57e66ecbdd2fddc9fbf3e984b1c523b70e9809
- Affected versionversion=eab0da38912ebdad922ed0388209f7eb0a5163cd <e6b5afd30b99b43682a7764e1a74a42fe4d5f4b3
What conditions does exploitation require?
What is affected?
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