CVE-2026-64033
Last modified
CVE-2026-64033 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. 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. EPSS estimates a 0.49% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.15.61, < 5.15.209 | — |
| Linux | Linux Kernel | >= 5.17, < 6.1.175 | — |
| Linux | Linux Kernel | >= 6.2, < 6.6.142 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.92 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.34 | — |
| Linux | Linux Kernel | >= 6.19, < 7.0.11 | — |
| Linux | Linux Kernel | 7.1 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64033?
How severe is CVE-2026-64033?
How do I fix CVE-2026-64033?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64028In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64029In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-6403The Quick Playground plugin for WordPress is vulnerable to P…7.5
- CVE-2026-64030In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-64031In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64032In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64034In the Linux kernel, the following vulnerability has been re…9.3
- CVE-2026-64035In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64036In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64037In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64038In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-64039In the Linux kernel, the following vulnerability has been re…7.7
Are you affected by CVE-2026-64033?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
