NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 39/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.48% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 00904a73272b9f3ef3952fe69a833909dccad1ef, 01e42aabaf7632beb4bf235c7238b96c746d4144, 5.15.209.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 00904a73272b9f3ef3952fe69a833909dccad1ef, 01e42aabaf7632beb4bf235c7238b96c746d4144, 5.15.209 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Published: Jul 19, 2026
Updated: Oct 13, 2026
EPSS: 0.4% · 41th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CNA vs NVD score

NVD: —
CNA · Linux: 9.8; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernel5.15.61 and later · before 5.15.209
linux linux kernel5.17 and later · before 6.1.175
linux linux kernel6.2 and later · before 6.6.142
linux linux kernel6.7 and later · before 6.12.92
linux linux kernel6.13 and later · before 6.18.34
linux linux kernel6.19 and later · before 7.0.11
linux linux kernel7.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 5.17affected
- bab17b761c8974a869b04462be5d4dd9aad366b4 and later · before 01e42aabaf7632beb4bf235c7238b96c746d4144affected · git
- ae4c81644e9105d9f7f713bb0d444737bb6a0cf1 and later · before 548f3956e53a7f7bde912d8129010b8986d5e602affected · git
- ae4c81644e9105d9f7f713bb0d444737bb6a0cf1 and later · before 00904a73272b9f3ef3952fe69a833909dccad1efaffected · git
- ae4c81644e9105d9f7f713bb0d444737bb6a0cf1 and later · before 92060ab1c5115674cf319175550f85f68405121faffected · git
- ae4c81644e9105d9f7f713bb0d444737bb6a0cf1 and later · before eae62c5451e67e8b033c1681fd3b85d7e9a9a28faffected · git
- ae4c81644e9105d9f7f713bb0d444737bb6a0cf1 and later · before b0e9706fb2859064bb6c677554c4d20c713aa8e0affected · git
- ae4c81644e9105d9f7f713bb0d444737bb6a0cf1 and later · before 5b74373390113fba798a76b483837029ab010fefaffected · git
- 5.15.61 and later · before 5.15.209affected · semver
- before 5.17not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.176-1	6.1.176-1
Debian:13	linux	before 6.12.94-1	6.12.94-1
Debian:14	linux	before 7.0.12-1	7.0.12-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2026-64031Jul 19, 2026 · erofs: fix managed cache race for unaligned extents
31Monitor
← EarlierCVE-2026-64032Jul 19, 2026 · bridge: mcast: Fix a possible use-after-free when removing a bridge port
31Monitor
Later →CVE-2026-64034Jul 19, 2026 · net: mana: Fix TOCTOU double-fetch of hwc_msg_id from DMA buffer
37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	00904a73272b9f3ef3952fe69a833909dccad1ef	Vendor (CNA)
Linux Linux	01e42aabaf7632beb4bf235c7238b96c746d4144	Vendor (CNA)
Linux Linux	5.15.209	Vendor (CNA)
Linux Linux	548f3956e53a7f7bde912d8129010b8986d5e602	Vendor (CNA)
Linux Linux	5b74373390113fba798a76b483837029ab010fef	Vendor (CNA)
Linux Linux	92060ab1c5115674cf319175550f85f68405121f	Vendor (CNA)
Linux Linux	b0e9706fb2859064bb6c677554c4d20c713aa8e0	Vendor (CNA)
Linux Linux	eae62c5451e67e8b033c1681fd3b85d7e9a9a28f	Vendor (CNA)
debian:linux	6.1.176-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-26-0576 · Jul 20, 2026(Linux Kernel Güvenlik Bildirimi)

All national notices →

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/00904a73272b9f3ef3952fe69a833909dccad1ef

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records