CVE-2026-92510

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 7.8; sources differ by 0.0.

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

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

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

RDMA/core: Fix potential use after free in ib_destroy_srq_user()

When accessing a SRQ via the netlink path the only synchronization mechanism for the said SRQ is rdma_restrack_get(). Currently, rdma_restrack_del() is invoked at the end of ib_destroy_srq_user(), which is too late, since by that point vendor-specific resources associated with the SRQ might already be freed. This can leave a short window where the SRQ remains accessible through restrack, leading to a potential use-after-free.

Fix this by moving the rdma_restrack_begin_del() call to the start of ib_destroy_srq_user(), ensuring that the SRQ is removed from restrack before its internal resources are released. This guarantees that no new users hold references to a SRQ that is in the process of destruction.

In addition, this change preserves the intended inverted order between create and destroy routines: resources are added to restrack at the end of successful creation, and hence shall be removed from the restrack first thing during the destruction flow, which keeps the lifecycle management consistent and predictable.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (6)

Auto-updated Sep 18, 2026
No patch confirmed yet.
generic

RDMA/core: Fix potential use after free in ib_destroy_srq_user() - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/core: Fix potential use after free in ib_destroy_srq_user() - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/core: Fix potential use after free in ib_destroy_srq_user() - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/core: Fix potential use after free in ib_destroy_srq_user() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9c704383529044c02122f85a2a9a42cbf14a07a6
generic

RDMA/core: Fix potential use after free in ib_destroy_srq_user() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/95c992c869df54a6a7061f5f3fb6400244f2af8f
generic

RDMA/core: Fix potential use after free in ib_destroy_srq_user() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/88244ecc71cc0b3ed200f5ef7ddea6686adfd730

Vendor Advisories for CVE-2026-92510(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-92510?
CVE-2026-92510 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/core: Fix potential use after free in ibdestroysrq_user() When accessing a SRQ via the netlink path the only synchronization mechanism for the said SRQ is rdmarestrackget(). Currently, rdmarestrackdel() is invoked at the end…
When was CVE-2026-92510 disclosed?
CVE-2026-92510 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92510 actively exploited?
CVE-2026-92510 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92510?
CVE-2026-92510 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92510?
No fix for CVE-2026-92510 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-92510 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-92510

Explore →

Is Your Infrastructure Affected by CVE-2026-92510?

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

Book a Demo →Browse All CVEs