Linux Kernel: Use-After-Free (CVE-2026-64033)
Published Last modified Sources: SUSE, Ubuntu, CVE.org, BSI
What is affected, what to do
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.
Update Linux Kernel to version 5.15.209, Linux Kernel to version 6.1.175, Linux Kernel to version 6.6.142.
- Affected
- Linux Kernel
lt 5.15.61..5.15.209 - Linux Kernel
lt 5.17..6.1.175 - Linux Kernel
lt 6.2..6.6.142 - Linux Kernel
lt 6.7..6.12.92 - Linux Kernel
lt 6.13..6.18.34 - Linux Kernel
lt 6.19..7.0.11
- Linux Kernel
- Fixed in
- Linux Kernel
5.15.209 - Linux Kernel
6.1.175 - Linux Kernel
6.6.142 - Linux Kernel
6.12.92 - Linux Kernel
6.18.34 - Linux Kernel
7.0.11 - Linux Kernel
7.1
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
9.8
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
9.8
CVSS v3
Severity Critical on the scale from 0 to 10.
Source: SUSE, Ubuntu, CVE.org, BSI
0.5 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 42.2
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 83.76 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 9.8 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 9.8
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.5 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 42.2
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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.
Source: suse_csaf, Ubuntu Security Notices, cvelistv5, NVD (NIST), CVE.org (MITRE), BSI WID Portal, BSI CSAF
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Linux | Linux |
|
|
Vendors and products
Affected operating systems
| Linux | ubuntu | linux-aws-fips | noble |
| Linux | ubuntu | linux-ibm-6.8 | jammy |
| Linux | linux | linux_kernel | 7.1 |
| Linux | linux | linux_kernel | — |
References & sources
- git.kernel.orgstable/c/01e42aabaf7632beb4bf235c7238b96c746d4144
- git.kernel.orgstable/c/548f3956e53a7f7bde912d8129010b8986d5e602
- git.kernel.orgstable/c/00904a73272b9f3ef3952fe69a833909dccad1ef
- git.kernel.orgstable/c/92060ab1c5115674cf319175550f85f68405121f
- git.kernel.orgstable/c/eae62c5451e67e8b033c1681fd3b85d7e9a9a28f
- git.kernel.orgstable/c/b0e9706fb2859064bb6c677554c4d20c713aa8e0
- git.kernel.orgstable/c/5b74373390113fba798a76b483837029ab010fef
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Initial analysis by NVDNVD
Newly listed as affected:- Linux Kernel (6.7 – before 6.12.92; 5.17 – before 6.1.175; 6.13 – before 6.18.34; 6.19 – before 7.0.11; 6.2 – before 6.6.142; 5.15.61 – before 5.15.209; 4 individual versions)
Weakness type: CWE-416
New references:- https://git.kernel.org/stable/c/00904a73272b9f3ef3952fe69a833909dccad1ef
- https://git.kernel.org/stable/c/01e42aabaf7632beb4bf235c7238b96c746d4144
- https://git.kernel.org/stable/c/548f3956e53a7f7bde912d8129010b8986d5e602
- https://git.kernel.org/stable/c/5b74373390113fba798a76b483837029ab010fef
and 3 more references
Show 9 original changes
Individual changes of this event as published by NVD Type Action Before After Weakness type (CWE) added —CWE-416Product configuration added —OR *cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.92 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.17 up to (excluding) 6.1.175 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.34 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 7.0.11 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.142 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.15.61 up to (excluding) 5.15.209Reference type added —kernel.org: https://git.kernel.org/stable/c/00904a73272b9f3ef3952fe69a833909dccad1ef Types: PatchReference type added —kernel.org: https://git.kernel.org/stable/c/01e42aabaf7632beb4bf235c7238b96c746d4144 Types: PatchReference type added —kernel.org: https://git.kernel.org/stable/c/548f3956e53a7f7bde912d8129010b8986d5e602 Types: PatchReference type added —kernel.org: https://git.kernel.org/stable/c/5b74373390113fba798a76b483837029ab010fef Types: PatchReference type added —kernel.org: https://git.kernel.org/stable/c/92060ab1c5115674cf319175550f85f68405121f Types: PatchReference type added —kernel.org: https://git.kernel.org/stable/c/b0e9706fb2859064bb6c677554c4d20c713aa8e0 Types: PatchReference type added —kernel.org: https://git.kernel.org/stable/c/eae62c5451e67e8b033c1681fd3b85d7e9a9a28f Types: PatchSource identifier: nvd@nist.gov
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-64033"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-64033.svg?lang=en" alt="CVE-2026-64033 – NEOSEC Intel" height="20"></a>