CVE-2026-90423

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/rxe: Fix UAF in ODP init error-handling path

rxe_odp_mr_init_user() stores &umem_odp->umem in mr->umem before calling rxe_odp_init_pages(). If rxe_odp_init_pages() fails, rxe_odp_mr_init_user() releases umem_odp and returns an error.

rxe_reg_user_mr() then unwinds the error through rxe_cleanup(), rxe_mr_cleanup(), ib_umem_release(mr->umem). There is an IS_ERR_OR_NULL(umem) check at the start of ib_umem_release(). But since mr->umem is NOT reset to NULL in the error handling path of rxe_odp_mr_init_user(), the check passes and it reads already-freed fields like umem->is_dmabuf, causing UAF.

Fix the UAF by clearing mr->umem after releasing the failed ODP umem so the MR cleanup path does not release it again.

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
6th
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 (3)

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

RDMA/rxe: Fix UAF in ODP init error-handling path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/51f2c8d2c99fc1f452f7113c08a35edcc4bf8732
generic

RDMA/rxe: Fix UAF in ODP init error-handling path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4cfb448705da3171d44d9cbe7be53ff03284d532
generic

RDMA/rxe: Fix UAF in ODP init error-handling path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5f1933163327c9f1c8f2a341c6cb551aaf231ff9

Vendor Advisories for CVE-2026-90423(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (178 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-90423?
CVE-2026-90423 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix UAF in ODP init error-handling path rxeodpmrinituser() stores &umem_odp->umem in mr->umem before calling rxeodpinitpages(). If rxeodpinitpages() fails, rxeodpmrinituser() releases umem_odp and returns an error.…
When was CVE-2026-90423 disclosed?
CVE-2026-90423 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-90423 actively exploited?
CVE-2026-90423 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90423?
CVE-2026-90423 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-90423?
No fix for CVE-2026-90423 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-90423 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-90423

Explore →

Is Your Infrastructure Affected by CVE-2026-90423?

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

Book a Demo →Browse All CVEs