CVE-2026-43041 json
net: qrtr: replace qrtr_tx_flow radix_tree with xarray to fix memory leak
published 2026-05-01 6 mo ago modified 2026-11-06 2 d ago also EUVD-2026-26640
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 1%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
net: qrtr: replace qrtr_tx_flow radix_tree with xarray to fix memory leak
__radix_tree_create() allocates and links intermediate nodes into the tree one by one. If a subsequent allocation fails, the already-linked nodes remain in the tree with no corresponding leaf entry. These orphaned internal nodes are never reclaimed because radix_tree_for_each_slot() only visits slots containing leaf values.
The radix_tree API is deprecated in favor of xarray. As suggested by Matthew Wilcox, migrate qrtr_tx_flow from radix_tree to xarray instead of fixing the radix_tree itself [1]. xarray properly handles cleanup of internal nodes — xa_destroy() frees all internal xarray nodes when the qrtr_node is released, preventing the leak.
[1] https://lore.kernel.org/all/20260225071623.41275-1-jiayuan.chen@linux.dev/T/
Patch / fix
- Linux Linux 5.10.253, 5.15.203, 6.1.168, 6.6.134, 6.12.81, 6.18.22, 6.19.12, 7.0
- linux Debian 12 6.1.170-1
- linux Debian 13 6.12.85-1
- linux Debian 14 6.19.12-1
debian advisories DEBIAN-CVE-2026-43041
- linux Ubuntu 22.04 LTS 5.15.0-186.196
- linux Ubuntu 24.04 LTS 6.8.0-136.136
- linux-aws Ubuntu 22.04 LTS 5.15.0-1112.119
- linux-aws Ubuntu 24.04 LTS 6.8.0-1061.64
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1112.122
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1064.72
- linux-gke Ubuntu 22.04 LTS 5.15.0-1108.114
- linux-gke Ubuntu 24.04 LTS 6.8.0-1059.67
ubuntu advisories UBUNTU-CVE-2026-43041
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/f2dd9aaf6e2861337f5835f877a5b2becaf4b015 commit
- git.kernel.org/stable/c/4b75ff0aedd6ade1018ad4a3a9d8336794e36e42 commit
- git.kernel.org/stable/c/ff134cc43972d7ddceff8cfd36cf6b9eaafc00b3 commit
- git.kernel.org/stable/c/0fda873092b541bb5a9b87d728a2429f863f8cfa commit
- git.kernel.org/stable/c/69402908e277dd164bf8d7c8fd0513c0fac28e9e commit
- git.kernel.org/stable/c/f2664bc4f0f356f17c2094587a2b3665e3867e44 commit
- git.kernel.org/stable/c/5d2249eefaca59908fe3c264b8eca526424dcfbe commit
- git.kernel.org/stable/c/2428083101f6883f979cceffa76cd8440751ffe6 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-43041 updated cvss 5.5
kernel: net: qrtr: replace qrtr_tx_flow radix_tree with xarray to fix memory leak
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 d ago
Exploit prediction
0.11% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-401 Missing Release of Memory after Effective Lifetime
- Technology feeds
References
-
git.kernel.org
/stable/c/f2dd9aaf6e2861337f5835f877a5b2becaf4b015
patch
-
git.kernel.org
/stable/c/4b75ff0aedd6ade1018ad4a3a9d8336794e36e42
patch
-
git.kernel.org
/stable/c/ff134cc43972d7ddceff8cfd36cf6b9eaafc00b3
patch
-
git.kernel.org
/stable/c/0fda873092b541bb5a9b87d728a2429f863f8cfa
patch
-
git.kernel.org
/stable/c/69402908e277dd164bf8d7c8fd0513c0fac28e9e
patch
-
git.kernel.org
/stable/c/f2664bc4f0f356f17c2094587a2b3665e3867e44
patch
-
git.kernel.org
/stable/c/5d2249eefaca59908fe3c264b8eca526424dcfbe
patch
-
git.kernel.org
/stable/c/2428083101f6883f979cceffa76cd8440751ffe6
patch
Sources
- CVE List CVE-2026-43041
- NVD CVE-2026-43041
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.