Kernel crash via unchecked mlx5 namespace lookup
Published Apr 1, 2025 · Updated May 11, 2026
NULL pointer dereference in the Linux kernel mlx5 flow-steering code allows local users to crash the system during flow-rule setup. mlx5_chains_create_table() dereferences a failed namespace lookup because it does not check error returns from mlx5_get_fdb_sub_ns() or mlx5_get_flow_namespace(). Reaching the path requires CAP_NET_ADMIN in the initial user namespace and TC offload or eswitch flow rules on a physical mlx5 device; the reported consequence is a kernel crash.
Summary
What happened
NULL pointer dereference in the Linux kernel mlx5 flow-steering code allows local users to crash the system during flow-rule setup. mlx5_chains_create_table() dereferences a failed namespace lookup because it does not check error returns from mlx5_get_fdb_sub_ns() or mlx5_get_flow_namespace(). Reaching the path requires CAP_NET_ADMIN in the initial user namespace and TC offload or eswitch flow rules on a physical mlx5 device; the reported consequence is a kernel crash.
The record
- CVE
- CVE-2025-21975
- Published
- Apr 1, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 1, 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=39ac237ce00968545e7298faa9e07ecb7e440fb5 <093b4aaec97ec048623e3fe1e516fc45a954d412
- Affected versionversion=39ac237ce00968545e7298faa9e07ecb7e440fb5 <1598307c914ba3d2642a2b03d1ff11efbdb7c6c2
- Affected versionversion=39ac237ce00968545e7298faa9e07ecb7e440fb5 <15bdd93728369b2c8942a8e5d549d4b5dc04a2d9
- Affected versionversion=39ac237ce00968545e7298faa9e07ecb7e440fb5 <1d34296409a519b4027750e3e82d9e19553a7398
- Affected versionversion=39ac237ce00968545e7298faa9e07ecb7e440fb5 <29c419c64e9b396baeda1d8713d2aa3ba7c0acf6
- Affected versionversion=39ac237ce00968545e7298faa9e07ecb7e440fb5 <637105ef0d46fe5beac15aceb431da3ec832bb00
- Affected versionversion=39ac237ce00968545e7298faa9e07ecb7e440fb5 <eab0396353be1c778eba1c0b5180176f04dd21ce
- Affected versionversion=5.6
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