CVE-2026-64033

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-19. the CNA's CVSS baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

RDMA/rtrs: Fix use-after-free in path file creation cleanup

In the error path of rtrs_srv_create_path_files(), the sysfs root folders may already have been created and srv_path->kobj may already have been initialized. If a later step fails, the cleanup currently calls kobject_put(&srv_path->kobj) before rtrs_srv_destroy_once_sysfs_root_folders(srv_path).

kobject_put() may drop the last reference to srv_path->kobj and invoke the release callback, rtrs_srv_release(), which frees srv_path. The following call to rtrs_srv_destroy_once_sysfs_root_folders(srv_path) then dereferences srv_path internally to access srv_path->srv, resulting in a use-after-free.

This failure path is reached before rtrs_srv_create_path_files() returns success, so the successful-path lifetime handling is not involved.

Fix this by destroying the sysfs root folders before calling kobject_put(&srv_path->kobj), so srv_path is still valid while the helper accesses it.

This issue was found by a static analysis tool I am developing.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

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%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Aug 26, 2026
No patch confirmed yet.
generic

RDMA/rtrs: Fix use-after-free in path file creation cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/rtrs: Fix use-after-free in path file creation cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/rtrs: Fix use-after-free in path file creation cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

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

RDMA/rtrs: Fix use-after-free in path file creation cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/92060ab1c5115674cf319175550f85f68405121f
generic

RDMA/rtrs: Fix use-after-free in path file creation cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/00904a73272b9f3ef3952fe69a833909dccad1ef
generic

RDMA/rtrs: Fix use-after-free in path file creation cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/548f3956e53a7f7bde912d8129010b8986d5e602
generic

RDMA/rtrs: Fix use-after-free in path file creation cleanup - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/01e42aabaf7632beb4bf235c7238b96c746d4144

Vendor Advisories for CVE-2026-64033(1)

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

Patch Availability(16)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(16)

Data Freshness Timeline

(refreshed 60× in last 7d / 346× 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 434 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64033?
CVE-2026-64033 is a critical vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs: Fix use-after-free in path file creation cleanup In the error path of rtrssrvcreatepathfiles(), the sysfs root folders may already have been created and srv_path->kobj may already have been initialized. If a later step…
When was CVE-2026-64033 disclosed?
CVE-2026-64033 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64033 actively exploited?
CVE-2026-64033 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.0% of all scored CVEs.
What is the CVSS score of CVE-2026-64033?
CVE-2026-64033 has a CVSS v4.0 base score of 9.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64033?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64033, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-64033?

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