CVE-2026-93224

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.1Exploit: 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:

svcrdma: Fix unmatched rn_unregister on failed accept

When svc_rdma_accept() takes the errout path before rpcrdma_rn_register() has succeeded, the existing cleanup block calls rpcrdma_rn_unregister(dev, &newxprt->sc_rn) unconditionally. svcxprt_rdma is kzalloc'd, so on that path sc_rn.rn_index is 0 and sc_rn.rn_done is NULL; the unregister therefore xa_erase()s another caller's slot 0 and performs an unmatched kref_put() on the rpcrdma_device's rd_kref.

The same errout also brackets the cleanup with svc_xprt_get()/ svc_xprt_put() around the kref_init() birth reference. The kref goes 1 -> 2 -> 1 and never reaches 0, so the svcxprt_rdma (and the net/ns_tracker it pinned) is leaked on every failed accept.

rpcrdma_rn_register() writes rn->rn_done last, only after xa_alloc() and kref_get() have both succeeded, so rn_done == NULL is a natural "never registered" sentinel. Guard rpcrdma_rn_unregister() with an early return when rn_done is NULL, and clear rn_done before the matching xa_erase() so a repeated unregister is also a no-op.

With that guard in place, the accept errout drops the kref_init() birth reference via svc_xprt_put(), which dispatches svc_rdma_free(). Teardown of sc_qp, sc_sq_cq, sc_rq_cq, and sc_pd runs under existing IS_ERR/NULL guards in svc_rdma_free(); sc_rn is covered by the new rn_done sentinel; sc_cm_id is non-NULL on every errout path because svc_rdma_accept() dereferences it above the first goto errout.

svc_xprt_free() drops the module reference associated with the freed transport, and svc_handle_xprt() drops its pre-acquired reference when ->xpo_accept() returns NULL. Take a replacement module reference before svc_xprt_put() so the two module_put()s remain balanced.

The rn_done guard also covers svc_rdma_free()'s non-listener call to rpcrdma_rn_unregister() for transports whose register attempt failed or never ran.

CVSS v3
8.1
EG Score
8.1HIGHhigh confidence
EG Risk
41
EG Risk 41/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
Severity81% × 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.5%
EPSS %ILE
37th
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 24, 2026

Last Modified

September 25, 2026

Advisory Details (4)

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

svcrdma: Fix unmatched rn_unregister on failed accept - kernel/git/stable/linux.git - Linux kernel stable tree

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

svcrdma: Fix unmatched rn_unregister on failed accept - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/45a444a17240f4fa2235f0dfd4a96fc80f1eb2c2
generic

svcrdma: Fix unmatched rn_unregister on failed accept - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/26190394c64c9429481fc88a4738f70bb92fb352
generic

svcrdma: Fix unmatched rn_unregister on failed accept - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0335800071a6dfdf7d21d729b5e7d8fa98936211

Vendor Advisories for CVE-2026-93224(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
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 25× in last 7d / 43× 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 07:02 UTCEG score recompute
  2. 2026-10-05 07:02 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 18:20 UTCGHSA enrichment
  5. 2026-10-04 05:37 UTCGHSA enrichment
  6. 2026-10-03 16:56 UTCEG score recompute
  7. 2026-10-03 16:56 UTCGHSA enrichment
  8. 2026-10-03 04:15 UTCEG score recompute
  9. 2026-10-03 04:15 UTCGHSA enrichment
  10. 2026-10-02 15:33 UTCGHSA enrichment
  11. 2026-10-02 02:52 UTCEG score recompute
  12. 2026-10-02 02:51 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 14:07 UTCGHSA enrichment
  15. 2026-10-01 01:26 UTCEG score recompute
  16. 2026-10-01 01:26 UTCGHSA enrichment
  17. 2026-09-30 15:04 UTCEPSS rescore
  18. 2026-09-30 12:44 UTCGHSA enrichment
  19. 2026-09-30 00:03 UTCEG score recompute
  20. 2026-09-30 00:03 UTCGHSA enrichment
  21. 2026-09-29 11:19 UTCGHSA enrichment
  22. 2026-09-28 22:31 UTCEG score recompute
  23. 2026-09-28 22:31 UTCGHSA enrichment
  24. 2026-09-28 13:52 UTCEPSS rescore
  25. 2026-09-28 13:52 UTCEPSS rescore
Show 18 more
  1. 2026-09-28 09:49 UTCGHSA enrichment
  2. 2026-09-27 21:08 UTCEG score recompute
  3. 2026-09-27 21:08 UTCGHSA enrichment
  4. 2026-09-27 13:49 UTCEPSS rescore
  5. 2026-09-27 08:27 UTCGHSA enrichment
  6. 2026-09-26 19:45 UTCEG score recompute
  7. 2026-09-26 19:44 UTCGHSA enrichment
  8. 2026-09-26 15:59 UTCEPSS rescore
  9. 2026-09-26 07:00 UTCEG score recompute
  10. 2026-09-26 06:59 UTCGHSA enrichment
  11. 2026-09-25 18:17 UTCEG score recompute
  12. 2026-09-25 18:17 UTCGHSA enrichment
  13. 2026-09-25 05:18 UTCEG score recompute▲ 8.10
  14. 2026-09-25 05:18 UTCGHSA enrichment
  15. 2026-09-25 05:16 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
  16. 2026-09-24 16:30 UTCNVD update
  17. 2026-09-24 15:32 UTCEG score recompute
  18. 2026-09-24 15:31 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93224?
CVE-2026-93224 is a high vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: svcrdma: Fix unmatched rn_unregister on failed accept When svcrdmaaccept() takes the errout path before rpcrdmarnregister() has succeeded, the existing cleanup block calls rpcrdmarnunregister(dev, &newxprt->sc_rn) unconditionally.…
When was CVE-2026-93224 disclosed?
CVE-2026-93224 was first published on September 24, 2026, with the most recent update on September 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-93224 actively exploited?
CVE-2026-93224 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93224?
CVE-2026-93224 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93224?
No fix for CVE-2026-93224 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-93224 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-93224

Explore →

Is Your Infrastructure Affected by CVE-2026-93224?

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