CVE-2026-97413

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.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/rtrs-srv: Fix integer underflow in process_read and process_write

usr_len is read from a network-supplied message field (le16_to_cpu) and used to compute data_len = off - usr_len without validating that usr_len <= off. A malicious RDMA client can send usr_len > off causing an integer underflow, resulting in data_len wrapping to a huge size_t value which is then passed to the rdma_ev callback as a memory length, leading to out-of-bounds memory access.

Fix by reading and validating usr_len <= off before rtrs_srv_get_ops_ids() in both process_read() and process_write(), ensuring the early return path acquires no reference and has no resource leak.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
49
EG Risk 49/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
Severity98% × 45%
Exploitation1% × 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
40th
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 total (CVSS ≥ 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

October 3, 2026

Advisory Details (6)

Auto-updated Oct 3, 2026
No patch confirmed yet.
generic

RDMA/rtrs-srv: Fix integer underflow in process_read and process_write - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/rtrs-srv: Fix integer underflow in process_read and process_write - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/rtrs-srv: Fix integer underflow in process_read and process_write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6b1e26e70d7ca9f0906af2283558a530eeb1f066
generic

RDMA/rtrs-srv: Fix integer underflow in process_read and process_write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/54bf38b27afc08a0eb6b732f9c14eb8a4bcb66b5
generic

RDMA/rtrs-srv: Fix integer underflow in process_read and process_write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c52b2afded988233cd4ccc185cf5147bbc77a76
generic

RDMA/rtrs-srv: Fix integer underflow in process_read and process_write - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24ad03bfeda05fca04c56677e57fd3d6bc3e9978

Vendor Advisories for CVE-2026-97413(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 102× in last 7d / 136× 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 136 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-97413?
CVE-2026-97413 is a critical vulnerability published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-srv: Fix integer underflow in processread and processwrite usrlen is read from a network-supplied message field (le16to_cpu) and used to compute datalen = off - usrlen without validating that usrlen <= off. A malicious…
When was CVE-2026-97413 disclosed?
CVE-2026-97413 was first published on September 24, 2026, with the most recent update on October 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-97413 actively exploited?
CVE-2026-97413 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-97413?
CVE-2026-97413 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-97413?
No fix for CVE-2026-97413 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-97413 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-97413

Explore →

Is Your Infrastructure Affected by CVE-2026-97413?

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