Skip to main content
VulnerabilityPublished Updated

CVE-2026-43041: Linux kernel · net: qrtr: replace qrtr_tx_flow radix_tree with xarray to fix memory leak

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ff134cc43972d7ddceff8cfd36cf6b9eaafc00b3 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:20 UTC

Severity
Low

Rated Low by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in ff134cc43972d7ddceff8cfd36cf6b9eaafc00b3, f2664bc4f0f356f17c2094587a2b3665e3867e44, f2dd9aaf6e2861337f5835f877a5b2becaf4b015 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 5fdeb0d372ab33b4175043a2a4a1730239a217f1, < ff134cc43972d7ddceff8cfd36cf6b9eaafc00b3
Fixed in
  • ff134cc43972d7ddceff8cfd36cf6b9eaafc00b3
LinuxLinuxAffected
  • ≥ 5fdeb0d372ab33b4175043a2a4a1730239a217f1, < f2664bc4f0f356f17c2094587a2b3665e3867e44
Fixed in
  • f2664bc4f0f356f17c2094587a2b3665e3867e44
LinuxLinuxAffected
  • ≥ 5fdeb0d372ab33b4175043a2a4a1730239a217f1, < f2dd9aaf6e2861337f5835f877a5b2becaf4b015
Fixed in
  • f2dd9aaf6e2861337f5835f877a5b2becaf4b015
LinuxLinuxAffected
  • ≥ 5fdeb0d372ab33b4175043a2a4a1730239a217f1, < 2428083101f6883f979cceffa76cd8440751ffe6
Fixed in
  • 2428083101f6883f979cceffa76cd8440751ffe6
LinuxLinuxAffected
  • ≥ 5fdeb0d372ab33b4175043a2a4a1730239a217f1, < 69402908e277dd164bf8d7c8fd0513c0fac28e9e
Fixed in
  • 69402908e277dd164bf8d7c8fd0513c0fac28e9e
LinuxLinuxAffected
  • ≥ 5fdeb0d372ab33b4175043a2a4a1730239a217f1, < 5d2249eefaca59908fe3c264b8eca526424dcfbe
Fixed in
  • 5d2249eefaca59908fe3c264b8eca526424dcfbe

AI-suggested

A fix is available and has been applied by migrating qrtr_tx_flow from radix_tree to xarray. Users should update to the fixed Linux kernel versions that include this change to prevent the memory leak.

Description

A memory leak vulnerability in the Linux kernel's net: qrtr component was fixed by replacing the deprecated radix_tree with xarray for managing qrtr_tx_flow. The issue involved orphaned internal nodes in the radix_tree that were not reclaimed on allocation failure, causing a memory leak. The migration to xarray ensures proper cleanup of internal nodes when the qrtr_node is released.

References

Community reviews

Loading reviews…