Kernel crash via unchecked device-memory pointer
Published Aug 22, 2025 · Updated May 11, 2026
NULL pointer dereference in the Linux kernel mlx5 driver allows local users to crash the kernel through device-memory handling. mlx5_init_once() can leave dev->dm as NULL when mlx5_dm_create() fails, yet later device-memory paths dereference it without validation. Reachability requires local interaction with mlx5 hardware; the reported consequence is a kernel crash, with no data exposure or privilege escalation.
Summary
What happened
NULL pointer dereference in the Linux kernel mlx5 driver allows local users to crash the kernel through device-memory handling. mlx5_init_once() can leave dev->dm as NULL when mlx5_dm_create() fails, yet later device-memory paths dereference it without validation. Reachability requires local interaction with mlx5 hardware; the reported consequence is a kernel crash, with no data exposure or privilege escalation.
The record
- CVE
- CVE-2025-38645
- Published
- Aug 22, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 22, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 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=5.4
- Affected versionversion=c9b9dcb430b3cd0ad2b04c360c4e528d73430481 <3046b011d368162b1b9ca9453eee0fea930e0a93
- Affected versionversion=c9b9dcb430b3cd0ad2b04c360c4e528d73430481 <4249f1307932f1b6bbb8b7eba60d82f0b7e44430
- Affected versionversion=c9b9dcb430b3cd0ad2b04c360c4e528d73430481 <62d7cf455c887941ed6f105cd430ba04ee0b6c9f
- Affected versionversion=c9b9dcb430b3cd0ad2b04c360c4e528d73430481 <70f238c902b8c0461ae6fbb8d1a0bbddc4350eea
- Affected versionversion=c9b9dcb430b3cd0ad2b04c360c4e528d73430481 <9053a69abfb5680c2a95292b96df5d204bc0776f
- Affected versionversion=c9b9dcb430b3cd0ad2b04c360c4e528d73430481 <da899a1fd7c40e2e4302af1db7d0b8540fb22283
- Affected versionversion=c9b9dcb430b3cd0ad2b04c360c4e528d73430481 <eebb225fe6c9103293807b8edabcbad59f9589bc
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