Kernel crash via mismatched RDMA QP comparison
Published Apr 16, 2025 · Updated Aug 5, 2026
NULL pointer dereference in Linux RDMA/mlx5 3.11 and later allows local users to crash the kernel through completion queue polling. mlx5_poll_one compares a firmware-supplied CQE QP number with mlx5_ib_qp rather than mlx5_core_qp, so it can retain the wrong cur_qp while handling a CQE. Reachability requires low-privileged local access and an active mlx5 RDMA configuration, especially management QPs 0 or 1; the demonstrated consequence is an availability-only kernel oops.
Summary
What happened
NULL pointer dereference in Linux RDMA/mlx5 3.11 and later allows local users to crash the kernel through completion queue polling. mlx5_poll_one compares a firmware-supplied CQE QP number with mlx5_ib_qp rather than mlx5_core_qp, so it can retain the wrong cur_qp while handling a CQE. Reachability requires low-privileged local access and an active mlx5 RDMA configuration, especially management QPs 0 or 1; the demonstrated consequence is an availability-only kernel oops.
The record
- CVE
- CVE-2025-22086
- Published
- Apr 16, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 16, 2025CVE 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=3.11
- Affected versionversion=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <3b97d77049856865ac5ce8ffbc6e716928310f7f
- Affected versionversion=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <55c65a64aefa6267b964d90e9a4039cb68ec73a5
- Affected versionversion=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <5ed3b0cb3f827072e93b4c5b6e2b8106fd7cccbd
- Affected versionversion=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <7c51a6964b45b6d40027abd77e89cef30d26dc5a
- Affected versionversion=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <856d9e5d72dc44eca6d5a153581c58fbd84e92e1
- Affected versionversion=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <cad677085274ecf9c7565b5bfc5d2e49acbf174c
- Affected versionversion=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <d52636eb13ccba448a752964cc6fc49970912874
- Affected versionversion=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <dc7139b7031d877acd73d7eff55670f22f48cd5e
- Affected versionversion=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <f0447ceb8a31d79bee7144f98f9a13f765531e1a
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