Local denial of service via QRTR memory leak
Published May 1, 2026 · Updated May 1, 2026
A memory leak in QRTR flow tracking in affected Linux Kernel releases allows local users to exhaust kernel memory through repeated allocations. If a later radix-tree node allocation fails, __radix_tree_create() leaves earlier internal nodes linked without leaf entries, so iteration never reclaims them. Triggering requires local low-privileged access; successful exhaustion degrades availability and can interrupt the host.
Summary
What happened
A memory leak in QRTR flow tracking in affected Linux Kernel releases allows local users to exhaust kernel memory through repeated allocations. If a later radix-tree node allocation fails, __radix_tree_create() leaves earlier internal nodes linked without leaf entries, so iteration never reclaims them. Triggering requires local low-privileged access; successful exhaustion degrades availability and can interrupt the host.
The record
- CVE
- CVE-2026-43041
- Published
- May 1, 2026
- Updated
- May 1, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, T1499.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2026CVE publishedPublication date reported by the CVE source.
- May 1, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.6
- Affected versionversion=5fdeb0d372ab33b4175043a2a4a1730239a217f1 <0fda873092b541bb5a9b87d728a2429f863f8cfa
- Affected versionversion=5fdeb0d372ab33b4175043a2a4a1730239a217f1 <2428083101f6883f979cceffa76cd8440751ffe6
- Affected versionversion=5fdeb0d372ab33b4175043a2a4a1730239a217f1 <4b75ff0aedd6ade1018ad4a3a9d8336794e36e42
- Affected versionversion=5fdeb0d372ab33b4175043a2a4a1730239a217f1 <5d2249eefaca59908fe3c264b8eca526424dcfbe
- Affected versionversion=5fdeb0d372ab33b4175043a2a4a1730239a217f1 <69402908e277dd164bf8d7c8fd0513c0fac28e9e
- Affected versionversion=5fdeb0d372ab33b4175043a2a4a1730239a217f1 <f2664bc4f0f356f17c2094587a2b3665e3867e44
- Affected versionversion=5fdeb0d372ab33b4175043a2a4a1730239a217f1 <f2dd9aaf6e2861337f5835f877a5b2becaf4b015
- Affected versionversion=5fdeb0d372ab33b4175043a2a4a1730239a217f1 <ff134cc43972d7ddceff8cfd36cf6b9eaafc00b3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo