Answer in brief
CVE-2025-22086 records a Unknown severity vulnerability in RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-22086 records a Unknown severity vulnerability in RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <3b97d77049856865ac5ce8ffbc6e716928310f7f || >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <856d9e5d72dc44eca6d5a153581c58fbd84e92e1 || >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <f0447ceb8a31d79bee7144f98f9a13f765531e1a || >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <dc7139b7031d877acd73d7eff55670f22f48cd5e || >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <7c51a6964b45b6d40027abd77e89cef30d26dc5a || >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <cad677085274ecf9c7565b5bfc5d2e49acbf174c || >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <55c65a64aefa6267b964d90e9a4039cb68ec73a5 || >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <d52636eb13ccba448a752964cc6fc49970912874 || >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <5ed3b0cb3f827072e93b4c5b6e2b8106fd7cccbd | 3b97d77049856865ac5ce8ffbc6e716928310f7f, 856d9e5d72dc44eca6d5a153581c58fbd84e92e1, f0447ceb8a31d79bee7144f98f9a13f765531e1a, dc7139b7031d877acd73d7eff55670f22f48cd5e, 7c51a6964b45b6d40027abd77e89cef30d26dc5a, cad677085274ecf9c7565b5bfc5d2e49acbf174c, 55c65a64aefa6267b964d90e9a4039cb68ec73a5, d52636eb13ccba448a752964cc6fc49970912874, 5ed3b0cb3f827072e93b4c5b6e2b8106fd7cccbd |
| Linux/Linuxgeneric | 3.11 | Not reported |
Published upstream
Apr 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow When cur_qp isn't NULL, in order to avoid fetching the QP from the radix tree again we check if the next cqe QP is identical to the one we already have. The bug however is that we are checking if the QP is identical by checking the QP number inside the CQE against the QP number inside the mlx5_ib_qp, but that's wrong since the QP number from the CQE is from FW so it should be matched against mlx5_core_qp which is our FW QP number. Otherwise we could use the wrong QP when handling a CQE which could cause the kernel trace below. This issue is mainly noticeable over QPs 0 & 1, since for now they are the only QPs in our driver whereas the QP number inside mlx5_ib_qp doesn't match the QP number inside mlx5_core_qp. BUG: kernel NULL pointer dereference, address: 0000000000000012 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP CPU: 0 UID: 0 PID: 7927 Comm: kworker/u62:1 Not tainted 6.14.0-rc3+ #189 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 Workqueue: ib-comp-unb-wq ib_cq_poll_work [ib_core] RIP: 0010:mlx5_ib_poll_cq+0x4c7/0xd90 [mlx5_ib] Code: 03 00 00 8d 58 ff 21 cb 66 39 d3 74 39 48 c7 c7 3c 89 6e a0 0f b7 db e8 b7 d2 b3 e0 49 8b 86 60 03 00 00 48 c7 c7 4a 89 6e a0 <0f> b7 5c 98 02 e8 9f d2 b3 e0 41 0f b7 86 78 03 00 00 83 e8 01 21 RSP: 0018:ffff88810511bd60 EFLAGS: 00010046 RAX: 0000000000000010 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffff88885fa1b3c0 RDI: ffffffffa06e894a RBP: 00000000000000b0 R08: 0000000000000000 R09: ffff88810511bc10 R10: 0000000000000001 R11: 0000000000000001 R12: ffff88810d593000 R13: ffff88810e579108 R14: ffff888105146000 R15: 00000000000000b0 FS: 0000000000000000(0000) GS:ffff88885fa00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000012 CR3: 00000001077e6001 CR4: 0000000000370eb0 Call Trace: <TASK> ? __die+0x20/0x60 ? page_fault_oops+0x150/0x3e0 ? exc_page_fault+0x74/0x130 ? asm_exc_page_fault+0x22/0x30 ? mlx5_ib_poll_cq+0x4c7/0xd90 [mlx5_ib] __ib_process_cq+0x5a/0x150 [ib_core] ib_cq_poll_work+0x31/0x90 [ib_core] process_one_work+0x169/0x320 worker_thread+0x288/0x3a0 ? work_busy+0xb0/0xb0 kthread+0xd7/0x1f0 ? kthreads_online_cpu+0x130/0x130 ? kthreads_online_cpu+0x130/0x130 ret_from_fork+0x2d/0x50 ? kthreads_online_cpu+0x130/0x130 ret_from_fork_asm+0x11/0x20 </TASK>
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <3b97d77049856865ac5ce8ffbc6e716928310f7f || >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <856d9e5d72dc44eca6d5a153581c58fbd84e92e1 || >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <f0447ceb8a31d79bee7144f98f9a13f765531e1a || >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <dc7139b7031d877acd73d7eff55670f22f48cd5e || >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <7c51a6964b45b6d40027abd77e89cef30d26dc5a || >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <cad677085274ecf9c7565b5bfc5d2e49acbf174c || >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <55c65a64aefa6267b964d90e9a4039cb68ec73a5 || >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <d52636eb13ccba448a752964cc6fc49970912874 || >=e126ba97dba9edeb6fafa3665b5f8497fc9cdf8c <5ed3b0cb3f827072e93b4c5b6e2b8106fd7cccbd | 3b97d77049856865ac5ce8ffbc6e716928310f7f, 856d9e5d72dc44eca6d5a153581c58fbd84e92e1, f0447ceb8a31d79bee7144f98f9a13f765531e1a, dc7139b7031d877acd73d7eff55670f22f48cd5e, 7c51a6964b45b6d40027abd77e89cef30d26dc5a, cad677085274ecf9c7565b5bfc5d2e49acbf174c, 55c65a64aefa6267b964d90e9a4039cb68ec73a5, d52636eb13ccba448a752964cc6fc49970912874, 5ed3b0cb3f827072e93b4c5b6e2b8106fd7cccbd |
| Linux/Linuxgeneric | 3.11 | Not reported |
Published upstream
Apr 16, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow When cur_qp isn't NULL, in order to avoid fetching the QP from the radix tree again we check if the next cqe QP is identical to the one we already have. The bug however is that we are checking if the QP is identical by checking the QP number inside the CQE against the QP number inside the mlx5_ib_qp, but that's wrong since the QP number from the CQE is from FW so it should be matched against mlx5_core_qp which is our FW QP number. Otherwise we could use the wrong QP when handling a CQE which could cause the kernel trace below. This issue is mainly noticeable over QPs 0 & 1, since for now they are the only QPs in our driver whereas the QP number inside mlx5_ib_qp doesn't match the QP number inside mlx5_core_qp. BUG: kernel NULL pointer dereference, address: 0000000000000012 #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: Oops: 0000 [#1] SMP CPU: 0 UID: 0 PID: 7927 Comm: kworker/u62:1 Not tainted 6.14.0-rc3+ #189 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 Workqueue: ib-comp-unb-wq ib_cq_poll_work [ib_core] RIP: 0010:mlx5_ib_poll_cq+0x4c7/0xd90 [mlx5_ib] Code: 03 00 00 8d 58 ff 21 cb 66 39 d3 74 39 48 c7 c7 3c 89 6e a0 0f b7 db e8 b7 d2 b3 e0 49 8b 86 60 03 00 00 48 c7 c7 4a 89 6e a0 <0f> b7 5c 98 02 e8 9f d2 b3 e0 41 0f b7 86 78 03 00 00 83 e8 01 21 RSP: 0018:ffff88810511bd60 EFLAGS: 00010046 RAX: 0000000000000010 RBX: 0000000000000000 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffff88885fa1b3c0 RDI: ffffffffa06e894a RBP: 00000000000000b0 R08: 0000000000000000 R09: ffff88810511bc10 R10: 0000000000000001 R11: 0000000000000001 R12: ffff88810d593000 R13: ffff88810e579108 R14: ffff888105146000 R15: 00000000000000b0 FS: 0000000000000000(0000) GS:ffff88885fa00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000012 CR3: 00000001077e6001 CR4: 0000000000370eb0 Call Trace: <TASK> ? __die+0x20/0x60 ? page_fault_oops+0x150/0x3e0 ? exc_page_fault+0x74/0x130 ? asm_exc_page_fault+0x22/0x30 ? mlx5_ib_poll_cq+0x4c7/0xd90 [mlx5_ib] __ib_process_cq+0x5a/0x150 [ib_core] ib_cq_poll_work+0x31/0x90 [ib_core] process_one_work+0x169/0x320 worker_thread+0x288/0x3a0 ? work_busy+0xb0/0xb0 kthread+0xd7/0x1f0 ? kthreads_online_cpu+0x130/0x130 ? kthreads_online_cpu+0x130/0x130 ret_from_fork+0x2d/0x50 ? kthreads_online_cpu+0x130/0x130 ret_from_fork_asm+0x11/0x20 </TASK>
Quoted source text, attributed separately from HOL analysis.