CVE-2023-53286

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2023-59903 (ENISA EUVD) · GHSA-fvfh-cc4q-w5cr (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 16, 2025

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Aug 5, 2026
Patch available.
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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 / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 5.10.192 (fixes >=5.8.0)—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (34 versions)
  • every version up to 5.10.197-1: fixed in 5.10.197-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)
  • every version up to 6.1.52-1: fixed in 6.1.52-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.13-1: fixed in 6.4.13-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.13-1: fixed in 6.4.13-1
—

Data Freshness Timeline

(refreshed 9× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 94 of 200 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 6 repeat rows among the latest 100 are merged into the row they repeat. The 106 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-06 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-11-05 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-11-04 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-11-03 16:41 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-11-03 02:50 UTCEG score recompute
  6. 2026-11-03 02:49 UTCGHSA enrichmentGHSA-fvfh-cc4q-w5cr · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-11-02 16:40 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-27 19:31 UTCEG score recompute
  14. 2026-10-27 19:31 UTCGHSA enrichmentGHSA-fvfh-cc4q-w5cr · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-25 17:28 UTCEG score recompute
  18. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-10-20 21:15 UTCEG score recompute
  24. 2026-10-20 21:15 UTCGHSA enrichmentGHSA-fvfh-cc4q-w5cr · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
Show 69 more
  1. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-19 14:55 UTCOSV refresh
  3. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-18 07:41 UTCEG score recompute
  5. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-12 18:12 UTCEG score recompute
  11. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-11 21:38 UTCEG score recompute
  13. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  20. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  21. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  22. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  23. 2026-09-30 16:37 UTCEG score recompute
  24. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  25. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  26. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  27. 2026-09-26 21:11 UTCOSV refresh
  28. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  29. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  30. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  31. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  32. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  33. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  34. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  35. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  36. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  37. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  38. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  39. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  40. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  41. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  42. 2026-09-07 06:48 UTCOSV refresh
  43. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  44. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  45. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  46. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  47. 2026-09-01 04:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  48. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  49. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  50. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  51. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  52. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  53. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  54. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  55. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  56. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  57. 2026-08-20 16:31 UTCOSV refresh
  58. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  59. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  60. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  61. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  62. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  63. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  64. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.1% · 4th percentile
  65. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  66. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  67. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  68. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  69. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.1% · 3rd percentile

Frequently asked(5)

What is CVE-2023-53286?
CVE-2023-53286 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2023-53286 published?
The CVE record for CVE-2023-53286 was published on September 16, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2023-53286 actively exploited?
CVE-2023-53286 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-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?
A fix for CVE-2023-53286 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs