CVE-2026-92507

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 — 3 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_dealloc_pd_user()

When accessing a PD via the netlink path the only synchronization mechanism for the said PD is rdma_restrack_get(). Currently, rdma_restrack_del() is invoked at the end of ib_dealloc_pd_user(), which is too late, since by that point vendor-specific resources associated with the PD might already be freed. This can leave a short window where the PD 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_dealloc_pd_user(), ensuring that the PD is removed from restrack before its internal resources are released. This guarantees that no new users hold references to a PD 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_dealloc_pd_user() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8b90e701342275f414e36e7421c502237df241ad
generic

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

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

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

https://git.kernel.org/stable/c/66d65f36d39759e9f62dc746dc71d862f20f827f
generic

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

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

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

https://git.kernel.org/stable/c/7647363fa02046da681acc3c827d9f301c06e0e7
generic

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

https://git.kernel.org/stable/c/df0e9efe61ca706a07b1c9bf93fcb9032455efc4

Vendor Advisories for CVE-2026-92507(1)

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 27× in last 7d / 72× 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.

  1. 2026-10-05 06:57 UTCEG score recompute
  2. 2026-10-05 06:57 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 19:00 UTCGHSA enrichment
  5. 2026-10-04 06:46 UTCGHSA enrichment
  6. 2026-10-03 18:49 UTCEG score recompute
  7. 2026-10-03 18:49 UTCGHSA enrichment
  8. 2026-10-03 06:17 UTCGHSA enrichment
  9. 2026-10-02 18:20 UTCEG score recompute
  10. 2026-10-02 18:20 UTCGHSA enrichment
  11. 2026-10-02 06:23 UTCEG score recompute
  12. 2026-10-02 06:23 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 18:26 UTCGHSA enrichment
  15. 2026-10-01 06:13 UTCGHSA enrichment
  16. 2026-09-30 18:17 UTCEG score recompute
  17. 2026-09-30 18:17 UTCGHSA enrichment
  18. 2026-09-30 15:04 UTCEPSS rescore
  19. 2026-09-30 06:20 UTCGHSA enrichment
  20. 2026-09-29 18:22 UTCEG score recompute
  21. 2026-09-29 18:22 UTCGHSA enrichment
  22. 2026-09-29 06:14 UTCEG score recompute
  23. 2026-09-29 06:14 UTCGHSA enrichment
  24. 2026-09-28 18:17 UTCEG score recompute
  25. 2026-09-28 18:17 UTCGHSA enrichment
Show 47 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 13:52 UTCEPSS rescore
  3. 2026-09-28 06:15 UTCGHSA enrichment
  4. 2026-09-27 18:18 UTCEG score recompute
  5. 2026-09-27 18:18 UTCGHSA enrichment
  6. 2026-09-27 13:49 UTCEPSS rescore
  7. 2026-09-27 06:21 UTCGHSA enrichment
  8. 2026-09-26 18:21 UTCEG score recompute
  9. 2026-09-26 18:21 UTCGHSA enrichment
  10. 2026-09-26 15:59 UTCEPSS rescore
  11. 2026-09-26 06:23 UTCEG score recompute
  12. 2026-09-26 06:23 UTCGHSA enrichment
  13. 2026-09-25 18:22 UTCGHSA enrichment
  14. 2026-09-25 06:00 UTCGHSA enrichment
  15. 2026-09-24 18:03 UTCEG score recompute
  16. 2026-09-24 18:03 UTCGHSA enrichment
  17. 2026-09-24 14:04 UTCEPSS rescore
  18. 2026-09-24 05:55 UTCGHSA enrichment
  19. 2026-09-23 17:58 UTCEG score recompute
  20. 2026-09-23 17:58 UTCGHSA enrichment
  21. 2026-09-23 17:54 UTCEPSS rescore
  22. 2026-09-23 06:01 UTCGHSA enrichment
  23. 2026-09-22 18:04 UTCEG score recompute
  24. 2026-09-22 18:04 UTCGHSA enrichment
  25. 2026-09-22 16:01 UTCEPSS rescore
  26. 2026-09-22 06:08 UTCEG score recompute
  27. 2026-09-22 06:07 UTCGHSA enrichment
  28. 2026-09-21 21:09 UTCEPSS rescore
  29. 2026-09-21 18:10 UTCGHSA enrichment
  30. 2026-09-21 06:13 UTCEG score recompute
  31. 2026-09-21 06:13 UTCGHSA enrichment
  32. 2026-09-20 20:16 UTCEPSS rescore
  33. 2026-09-20 18:16 UTCGHSA enrichment
  34. 2026-09-20 06:20 UTCGHSA enrichment
  35. 2026-09-19 18:23 UTCEG score recompute
  36. 2026-09-19 18:23 UTCGHSA enrichment
  37. 2026-09-19 06:26 UTCEG score recompute
  38. 2026-09-19 06:26 UTCGHSA enrichment
  39. 2026-09-18 19:28 UTCEPSS rescore
  40. 2026-09-18 18:30 UTCEG score recompute
  41. 2026-09-18 18:30 UTCGHSA enrichment
  42. 2026-09-18 18:01 UTCEG score recompute▲ 7.80
  43. 2026-09-18 18:01 UTCGHSA enrichment
  44. 2026-09-18 17:59 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  45. 2026-09-17 17:24 UTCNVD update
  46. 2026-09-17 16:23 UTCEG score recompute
  47. 2026-09-17 16:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92507?
CVE-2026-92507 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 ibdeallocpd_user() When accessing a PD via the netlink path the only synchronization mechanism for the said PD is rdmarestrackget(). Currently, rdmarestrackdel() is invoked at the end of…
When was CVE-2026-92507 disclosed?
CVE-2026-92507 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-92507 actively exploited?
CVE-2026-92507 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-92507?
CVE-2026-92507 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-92507?
No fix for CVE-2026-92507 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-92507 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-92507

Explore →

Is Your Infrastructure Affected by CVE-2026-92507?

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

Book a Demo →Browse All CVEs