CVE-2025-22086

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-04-16. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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: ? __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

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

April 16, 2025

Last Modified

August 5, 2026

Advisory Details (10)

Auto-updated Aug 2, 2026
Patch available.
generic Patch Available

[SECURITY] [DLA 4178-1] linux security update

https://lists.debian.org/debian-lts-announce/2025/05/msg00030.html
generic

RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f0447ceb8a31d79bee7144f98f9a13f765531e1a
generic

RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dc7139b7031d877acd73d7eff55670f22f48cd5e
generic

RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d52636eb13ccba448a752964cc6fc49970912874
generic

RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cad677085274ecf9c7565b5bfc5d2e49acbf174c
generic

RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/856d9e5d72dc44eca6d5a153581c58fbd84e92e1
generic

RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c51a6964b45b6d40027abd77e89cef30d26dc5a
generic

RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5ed3b0cb3f827072e93b4c5b6e2b8106fd7cccbd
generic

RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/55c65a64aefa6267b964d90e9a4039cb68ec73a5
generic

RDMA/mlx5: Fix mlx5_poll_one() cur_qp update flow - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b97d77049856865ac5ce8ffbc6e716928310f7f

Vendor Advisories for CVE-2025-22086(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1065 (5.4.0-1065.69) @ focal2026-05-30ubuntu
ubuntulinux-tools-gcp-fips (5.4.0.1150.92) @ focal2026-05-30ubuntu
ubuntulinux-tools-realtime (5.15.0.1086.90) @ jammy2026-05-30ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1083.89~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1050.54) @ jammy2026-05-30ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.142.137) @ jammy2026-05-30ubuntu
ubuntulinux-tools-gcp-fips (5.15.0.1085.75) @ jammy2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-22.22) @ plucky2026-05-30ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1086.89) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-fips (5.15.0.1091.76) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1091.89) @ jammy2026-05-30ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.142.152~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.218.238~18.04.1) @ bionic2026-05-30ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1091.100~20.04.1) @ focal2026-05-30ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1024.24) @ noble2026-05-30ubuntu
ubuntulinux-tools-azure (6.14.0-1007.7) @ plucky2026-05-30ubuntu
ubuntulinux-tools-azure-edge (5.4.0.1152.159~18.04.1) @ bionic2026-05-30ubuntu
ubuntulinux-tools-fips (5.4.0.1121.118) @ focal2026-05-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-28.28) @ oracular2026-05-30ubuntu
ubuntulinux-tools-bluefield (5.4.0.1106.102) @ focal2026-05-30ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1130.161) @ focal2026-05-30ubuntu
ubuntulinux-tools-oracle-64k (6.14.0-1007.7) @ plucky2026-05-30ubuntu
ubuntulinux-tools-lowlatency-64k (6.11.0-1015.16) @ oracular2026-05-30ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1081.81) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-edge (6.11.0-1018.18~24.04.1) @ noble2026-05-30ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1080.78) @ jammy2026-05-30ubuntu
ubuntulinux-tools-azure-nvidia-lts-24.04 (6.8.0-1029.32) @ noble2026-05-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-86.87~22.04.1) @ jammy2026-05-30ubuntu
redhatkernel-0:6.12.0-124.8.1.el10_12025-11-11redhat
redhatkernel-0:5.14.0-611.5.1.el9_72025-11-11redhat
linuxKernel @ 5.4.292—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (45 versions)5.10.237-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.129-1~deb11u1 (7 versions)6.1.137-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (37 versions)6.1.135-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.12.25-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.12.25-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(23)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 153 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 14:06 UTCEPSS rescore
  3. 2026-09-16 05:13 UTCEPSS rescore
  4. 2026-09-15 03:09 UTCEPSS rescore
  5. 2026-09-13 16:46 UTCEPSS rescore
  6. 2026-09-12 15:00 UTCEPSS rescore
  7. 2026-09-11 14:51 UTCEPSS rescore
  8. 2026-09-11 09:35 UTCEPSS rescore
  9. 2026-09-10 09:33 UTCEPSS rescore
  10. 2026-09-08 21:59 UTCEPSS rescore
  11. 2026-09-07 16:00 UTCEPSS rescore
  12. 2026-09-07 12:48 UTCOSV refresh
  13. 2026-09-06 13:46 UTCEPSS rescore
  14. 2026-09-06 13:46 UTCEPSS rescore
  15. 2026-09-05 15:28 UTCEPSS rescore
  16. 2026-09-04 05:05 UTCEPSS rescore
  17. 2026-09-02 14:11 UTCEPSS rescore
  18. 2026-09-01 13:52 UTCEPSS rescore
  19. 2026-09-01 04:38 UTCEPSS rescore
  20. 2026-08-30 19:16 UTCEPSS rescore
  21. 2026-08-30 01:21 UTCEPSS rescore
  22. 2026-08-28 21:40 UTCEPSS rescore
  23. 2026-08-27 14:24 UTCEPSS rescore
  24. 2026-08-25 13:47 UTCEPSS rescore
  25. 2026-08-23 00:18 UTCEPSS rescore
Show 75 more
  1. 2026-08-21 23:48 UTCEPSS rescore
  2. 2026-08-20 22:54 UTCEPSS rescore
  3. 2026-08-20 22:01 UTCOSV refresh
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:47 UTCEPSS rescore
  6. 2026-08-17 13:46 UTCEPSS rescore
  7. 2026-08-16 14:55 UTCEPSS rescore
  8. 2026-08-16 02:13 UTCEPSS rescore
  9. 2026-08-16 02:13 UTCEPSS rescore
  10. 2026-08-15 01:29 UTCEPSS rescore
  11. 2026-08-13 21:59 UTCEPSS rescore
  12. 2026-08-12 13:50 UTCEPSS rescore
  13. 2026-08-10 23:59 UTCEPSS rescore
  14. 2026-08-09 13:45 UTCEPSS rescore
  15. 2026-08-07 16:26 UTCEPSS rescore
  16. 2026-08-06 13:46 UTCEPSS rescore
  17. 2026-08-05 19:16 UTCEPSS rescore
  18. 2026-08-05 13:58 UTCEG score recompute
  19. 2026-08-05 13:58 UTCVendor advisory
  20. 2026-08-05 13:58 UTCGHSA enrichment
  21. 2026-08-04 15:09 UTCEPSS rescore
  22. 2026-08-04 10:37 UTCEPSS rescore
  23. 2026-08-03 10:35 UTCEPSS rescore
  24. 2026-08-02 02:25 UTCEPSS rescore
  25. 2026-08-01 04:15 UTCEPSS rescore
  26. 2026-07-30 16:27 UTCEPSS rescore
  27. 2026-07-30 07:14 UTCEG score recompute
  28. 2026-07-30 07:14 UTCVendor advisory
  29. 2026-07-30 07:14 UTCGHSA enrichment
  30. 2026-07-30 01:29 UTCEPSS rescore
  31. 2026-07-28 15:35 UTCEPSS rescore
  32. 2026-07-27 14:12 UTCEPSS rescore
  33. 2026-07-26 14:53 UTCEPSS rescore
  34. 2026-07-25 14:17 UTCEPSS rescore
  35. 2026-07-24 09:11 UTCOSV refresh
  36. 2026-07-23 14:17 UTCEPSS rescore
  37. 2026-07-23 02:50 UTCEG score recompute
  38. 2026-07-22 14:07 UTCEPSS rescore
  39. 2026-07-22 14:07 UTCEPSS rescore
  40. 2026-07-21 15:24 UTCEPSS rescore
  41. 2026-07-20 17:07 UTCEPSS rescore
  42. 2026-07-19 14:30 UTCEPSS rescore
  43. 2026-07-19 14:30 UTCEPSS rescore
  44. 2026-07-19 02:28 UTCEPSS rescore
  45. 2026-07-19 02:28 UTCEPSS rescore
  46. 2026-07-18 10:03 UTCEPSS rescore
  47. 2026-07-16 17:02 UTCEPSS rescore
  48. 2026-07-15 16:57 UTCEPSS rescore
  49. 2026-07-15 16:57 UTCEPSS rescore
  50. 2026-07-15 01:59 UTCEPSS rescore
  51. 2026-07-13 22:29 UTCEPSS rescore
  52. 2026-07-13 22:29 UTCEPSS rescore
  53. 2026-07-13 06:12 UTCEPSS rescore
  54. 2026-07-13 06:12 UTCEPSS rescore
  55. 2026-07-12 05:46 UTCEPSS rescore
  56. 2026-07-12 05:46 UTCEPSS rescore
  57. 2026-07-11 08:27 UTCEPSS rescore
  58. 2026-07-11 08:26 UTCEPSS rescore
  59. 2026-07-09 19:09 UTCEPSS rescore
  60. 2026-07-08 15:14 UTCEPSS rescore
  61. 2026-07-07 13:45 UTCEPSS rescore
  62. 2026-07-07 04:51 UTCOSV refresh
  63. 2026-07-06 16:26 UTCEPSS rescore
  64. 2026-07-06 02:22 UTCEPSS rescore
  65. 2026-07-06 02:22 UTCEPSS rescore
  66. 2026-07-05 02:30 UTCEPSS rescore
  67. 2026-07-04 06:30 UTCEPSS rescore
  68. 2026-07-01 15:06 UTCEPSS rescore
  69. 2026-06-30 23:21 UTCEPSS rescore
  70. 2026-06-30 23:21 UTCEPSS rescore
  71. 2026-06-29 14:06 UTCEPSS rescore
  72. 2026-06-28 14:07 UTCEPSS rescore
  73. 2026-06-28 14:07 UTCEPSS rescore
  74. 2026-06-28 04:55 UTCEPSS rescore
  75. 2026-06-28 04:55 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-22086?
CVE-2025-22086 is a medium vulnerability published on April 16, 2025. In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Fix mlx5pollone() 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…
When was CVE-2025-22086 disclosed?
CVE-2025-22086 was first published in the National Vulnerability Database on April 16, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-22086 actively exploited?
CVE-2025-22086 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.2% of all scored CVEs.
What is the CVSS score of CVE-2025-22086?
CVE-2025-22086 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-22086?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-22086, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-22086

Explore →

Is Your Infrastructure Affected by CVE-2025-22086?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs