CVE-2023-53286

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-09-16. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 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

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

RDMA/mlx5: Return the firmware result upon destroying QP/RQ

Previously when destroying a QP/RQ, the result of the firmware destruction function was ignored and upper layers weren't informed about the failure. Which in turn could lead to various problems since when upper layer isn't aware of the failure it continues its operation thinking that the related QP/RQ was successfully destroyed while it actually wasn't, which could lead to the below kernel WARN.

Currently, we return the correct firmware destruction status to upper layers which in case of the RQ would be mlx5_ib_destroy_wq() which was already capable of handling RQ destruction failure or in case of a QP to destroy_qp_common(), which now would actually warn upon qp destruction failure.

WARNING: CPU: 3 PID: 995 at drivers/infiniband/core/rdma_core.c:940 uverbs_destroy_ufile_hw+0xcb/0xe0 [ib_uverbs] Modules linked in: xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xt_addrtype iptable_nat nf_nat br_netfilter rpcrdma rdma_ucm ib_iser libiscsi scsi_transport_iscsi rdma_cm ib_umad ib_ipoib iw_cm ib_cm mlx5_ib ib_uverbs ib_core overlay mlx5_core fuse CPU: 3 PID: 995 Comm: python3 Not tainted 5.16.0-rc5+ #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 RIP: 0010:uverbs_destroy_ufile_hw+0xcb/0xe0 [ib_uverbs] Code: 41 5c 41 5d 41 5e e9 44 34 f0 e0 48 89 df e8 4c 77 ff ff 49 8b 86 10 01 00 00 48 85 c0 74 a1 4c 89 e7 ff d0 eb 9a 0f 0b eb c1 <0f> 0b be 04 00 00 00 48 89 df e8 b6 f6 ff ff e9 75 ff ff ff 90 0f RSP: 0018:ffff8881533e3e78 EFLAGS: 00010287 RAX: ffff88811b2cf3e0 RBX: ffff888106209700 RCX: 0000000000000000 RDX: ffff888106209780 RSI: ffff8881533e3d30 RDI: ffff888109b101a0 RBP: 0000000000000001 R08: ffff888127cb381c R09: 0de9890000000009 R10: ffff888127cb3800 R11: 0000000000000000 R12: ffff888106209780 R13: ffff888106209750 R14: ffff888100f20660 R15: 0000000000000000 FS: 00007f8be353b740(0000) GS:ffff88852c980000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f8bd5b117c0 CR3: 000000012cd8a004 CR4: 0000000000370ea0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ib_uverbs_close+0x1a/0x90 [ib_uverbs] __fput+0x82/0x230 task_work_run+0x59/0x90 exit_to_user_mode_prepare+0x138/0x140 syscall_exit_to_user_mode+0x1d/0x50 ? __x64_sys_close+0xe/0x40 do_syscall_64+0x4a/0x90 entry_SYSCALL_64_after_hwframe+0x44/0xae RIP: 0033:0x7f8be3ae0abb Code: 03 00 00 00 0f 05 48 3d 00 f0 ff ff 77 41 c3 48 83 ec 18 89 7c 24 0c e8 83 43 f9 ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 89 44 24 0c e8 c1 43 f9 ff 8b 44 RSP: 002b:00007ffdb51909c0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003 RAX: 0000000000000000 RBX: 0000557bb7f7c020 RCX: 00007f8be3ae0abb RDX: 0000557bb7c74010 RSI: 0000557bb7f14ca0 RDI: 0000000000000005 RBP: 0000557bb7fbd598 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000293 R12: 0000557bb7fbd5b8 R13: 0000557bb7fbd5a8 R14: 0000000000001000 R15: 0000557bb7f7c020

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

Published

September 16, 2025

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

RDMA/mlx5: Return the firmware result upon destroying QP/RQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/22664c06e997087fe37f9ba208008c948571214a
generic

RDMA/mlx5: Return the firmware result upon destroying QP/RQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/04704c201bb08efaf96d7b1396c6864f8984e244
generic

RDMA/mlx5: Return the firmware result upon destroying QP/RQ - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/mlx5: Return the firmware result upon destroying QP/RQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1a650d3ccd79cdd5796edd864683a6b8dd0bf576
generic

RDMA/mlx5: Return the firmware result upon destroying QP/RQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/73311dd831858d797cf8ebe140654ed519b41c36

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.192—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.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2023-53286?
CVE-2023-53286 is a high vulnerability published on September 16, 2025. In the Linux kernel, the following vulnerability has been resolved: RDMA/mlx5: Return the firmware result upon destroying QP/RQ Previously when destroying a QP/RQ, the result of the firmware destruction function was ignored and upper layers weren't informed about the failure. Which in turn could…
When was CVE-2023-53286 disclosed?
CVE-2023-53286 was first published in the National Vulnerability Database on September 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-2023-53286 actively exploited?
CVE-2023-53286 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 96.0% of all scored CVEs.
What is the CVSS score of CVE-2023-53286?
CVE-2023-53286 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-53286?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53286, 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

Explore the affected products and dependency analysis for CVE-2023-53286

Explore →

Is Your Infrastructure Affected by CVE-2023-53286?

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

Start Free Scan →Browse All CVEs