CVE-2026-64033

CRITICALCVSS 9.8/10EPSS 0.49%

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

CVSS 3.1
9.8/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS Probability
0.49%

39.4th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= bab17b761c8974a869b04462be5d4dd9aad366b4, < 01e42aabaf7632beb4bf235c7238b96c746d4144; >= ae4c81644e9105d9f7f713bb0d444737bb6a0cf1, < 548f3956e53a7f7bde912d8129010b8986d5e602; >= ae4c81644e9105d9f7f713bb0d444737bb6a0cf1, < 00904a73272b9f3ef3952fe69a833909dccad1ef; >= ae4c81644e9105d9f7f713bb0d444737bb6a0cf1, < 92060ab1c5115674cf319175550f85f68405121f; >= ae4c81644e9105d9f7f713bb0d444737bb6a0cf1, < eae62c5451e67e8b033c1681fd3b85d7e9a9a28f; >= ae4c81644e9105d9f7f713bb0d444737bb6a0cf1, < b0e9706fb2859064bb6c677554c4d20c713aa8e0; >= ae4c81644e9105d9f7f713bb0d444737bb6a0cf1, < 5b74373390113fba798a76b483837029ab010fef; >= 5.15.61, < 5.15.209
LinuxLinux5.17

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is CVE-2026-64033?
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.
How severe is CVE-2026-64033?
CVE-2026-64033 has a CVSS score of 9.8/10 (CRITICAL severity). The EPSS model estimates a 0.49% probability of exploitation in the next 30 days.
How do I fix CVE-2026-64033?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-64033?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST