CVE-2026-45910

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

RDMA/rxe: Fix race condition in QP timer handlers

I encontered the following warning: WARNING: drivers/infiniband/sw/rxe/rxe_task.c:249 at rxe_sched_task+0x1c8/0x238 [rdma_rxe], CPU#0: swapper/0/0 ... libsha1 [last unloaded: ip6_udp_tunnel] CPU: 0 UID: 0 PID: 0 Comm: swapper/0 Tainted: G C 6.19.0-rc5-64k-v8+ #37 PREEMPT Tainted: [C]=CRAP Hardware name: Raspberry Pi 4 Model B Rev 1.2 Call trace: rxe_sched_task+0x1c8/0x238 [rdma_rxe] (P) retransmit_timer+0x130/0x188 [rdma_rxe] call_timer_fn+0x68/0x4d0 __run_timers+0x630/0x888 ... WARNING: drivers/infiniband/sw/rxe/rxe_task.c:38 at rxe_sched_task+0x1c0/0x238 [rdma_rxe], CPU#0: swapper/0/0 ... WARNING: drivers/infiniband/sw/rxe/rxe_task.c:111 at do_work+0x488/0x5c8 [rdma_rxe], CPU#3: kworker/u17:4/93400 ... refcount_t: underflow; use-after-free. WARNING: lib/refcount.c:28 at refcount_warn_saturate+0x138/0x1a0, CPU#3: kworker/u17:4/93400

The issue is caused by a race condition between retransmit_timer() and rxe_destroy_qp, leading to the Queue Pair's (QP) reference count dropping to zero during timer handler execution.

It seems this warning is harmless because rxe_qp_do_cleanup() will flush all pending timers and requests.

Example of flow causing the issue:

CPU0 CPU1 retransmit_timer() { spin_lock_irqsave rxe_destroy_qp() __rxe_cleanup() __rxe_put() // qp->ref_count decrease to 0 rxe_qp_do_cleanup() { if (qp->valid) { rxe_sched_task() { WARN_ON(rxe_read(task->qp) <= 0); } } spin_unlock_irqrestore } spin_lock_irqsave qp->valid = 0 spin_unlock_irqrestore }

Ensure the QP's reference count is maintained and its validity is checked within the timer callbacks by adding calls to rxe_get(qp) and corresponding rxe_put(qp) after use.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

May 27, 2026

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

RDMA/rxe: Fix race condition in QP timer handlers - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/rxe: Fix race condition in QP timer handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/87bf646921430e303176edc4eb07c30160361b73
generic

RDMA/rxe: Fix race condition in QP timer handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/756c93d6df7c3bc599f6590b8e5afead6a41de1c
generic

RDMA/rxe: Fix race condition in QP timer handlers - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/rxe: Fix race condition in QP timer handlers - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-45910(1)

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

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-09-14ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-14ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-14ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-09-14ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-14ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-14ubuntu
linuxKernel @ 6.6.128—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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (103 versions)6.18.14-1—

Weakness Classification(1)

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

All Vendor Advisories

(12)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× 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 244 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-45910?
CVE-2026-45910 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix race condition in QP timer handlers I encontered the following warning: WARNING: drivers/infiniband/sw/rxe/rxetask.c:249 at rxeschedtask+0x1c8/0x238 [rdmarxe], CPU#0: swapper/0/0 ... libsha1 [last unloaded:…
When was CVE-2026-45910 disclosed?
CVE-2026-45910 was first published in the National Vulnerability Database on May 27, 2026, 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-2026-45910 actively exploited?
CVE-2026-45910 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 98.9% of all scored CVEs.
What is the CVSS score of CVE-2026-45910?
CVE-2026-45910 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-45910?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45910, 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-2026-45910

Explore →

Is Your Infrastructure Affected by CVE-2026-45910?

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

Start Free Scan →Browse All CVEs