CVE-2026-43041

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-01. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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/[email protected]/T/

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 8, 2026

Advisory Details (8)

Auto-updated Jun 14, 2026
No patch confirmed yet.
generic

net: qrtr: replace qrtr_tx_flow radix_tree with xarray to fix memory leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ff134cc43972d7ddceff8cfd36cf6b9eaafc00b3
generic

net: qrtr: replace qrtr_tx_flow radix_tree with xarray to fix memory leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f2dd9aaf6e2861337f5835f877a5b2becaf4b015
generic

net: qrtr: replace qrtr_tx_flow radix_tree with xarray to fix memory leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f2664bc4f0f356f17c2094587a2b3665e3867e44
generic

net: qrtr: replace qrtr_tx_flow radix_tree with xarray to fix memory leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/69402908e277dd164bf8d7c8fd0513c0fac28e9e
generic

net: qrtr: replace qrtr_tx_flow radix_tree with xarray to fix memory leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5d2249eefaca59908fe3c264b8eca526424dcfbe
generic

net: qrtr: replace qrtr_tx_flow radix_tree with xarray to fix memory leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4b75ff0aedd6ade1018ad4a3a9d8336794e36e42
generic

net: qrtr: replace qrtr_tx_flow radix_tree with xarray to fix memory leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2428083101f6883f979cceffa76cd8440751ffe6
generic

net: qrtr: replace qrtr_tx_flow radix_tree with xarray to fix memory leak - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0fda873092b541bb5a9b87d728a2429f863f8cfa

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-26 14:54 UTCEPSS rescore
  2. 2026-07-26 14:54 UTCEPSS rescore
  3. 2026-07-25 14:18 UTCEPSS rescore
  4. 2026-07-24 14:17 UTCEPSS rescore
  5. 2026-07-23 14:18 UTCEPSS rescore
  6. 2026-07-23 03:13 UTCEG score recompute
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-21 15:24 UTCEPSS rescore
  9. 2026-07-20 17:08 UTCEPSS rescore
  10. 2026-07-19 19:18 UTCOSV refresh
  11. 2026-07-19 14:31 UTCEPSS rescore
  12. 2026-07-19 02:29 UTCEPSS rescore
  13. 2026-07-18 10:04 UTCEPSS rescore
  14. 2026-07-16 17:03 UTCEPSS rescore
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-13 22:30 UTCEPSS rescore
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-12 05:46 UTCEPSS rescore
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-08 15:16 UTCEPSS rescore
  21. 2026-07-07 13:46 UTCEPSS rescore
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-05 02:30 UTCEPSS rescore
  25. 2026-07-04 06:31 UTCEPSS rescore
Show 68 more
  1. 2026-07-01 15:06 UTCEPSS rescore
  2. 2026-06-30 23:22 UTCEPSS rescore
  3. 2026-06-29 14:06 UTCEPSS rescore
  4. 2026-06-28 14:07 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-25 13:49 UTCEPSS rescore
  8. 2026-06-25 13:49 UTCEPSS rescore
  9. 2026-06-24 14:05 UTCEPSS rescore
  10. 2026-06-23 21:33 UTCEPSS rescore
  11. 2026-06-22 14:25 UTCEPSS rescore
  12. 2026-06-22 14:25 UTCEPSS rescore
  13. 2026-06-21 01:59 UTCEPSS rescore
  14. 2026-06-19 19:25 UTCEPSS rescore
  15. 2026-06-18 17:52 UTCEPSS rescore
  16. 2026-06-18 17:52 UTCEPSS rescore
  17. 2026-06-17 17:53 UTCEPSS rescore
  18. 2026-06-16 17:52 UTCEPSS rescore
  19. 2026-06-15 17:49 UTCEPSS rescore
  20. 2026-06-14 08:49 UTCGHSA enrichment
  21. 2026-06-13 23:00 UTCEPSS rescore
  22. 2026-06-12 23:12 UTCEPSS rescore
  23. 2026-06-12 23:12 UTCEPSS rescore
  24. 2026-06-12 10:21 UTCGHSA enrichment
  25. 2026-06-11 14:00 UTCEPSS rescore
  26. 2026-06-11 07:21 UTCGHSA enrichment
  27. 2026-06-10 22:18 UTCEPSS rescore
  28. 2026-06-10 05:05 UTCGHSA enrichment
  29. 2026-06-09 02:49 UTCGHSA enrichment
  30. 2026-06-08 14:17 UTCEPSS rescore
  31. 2026-06-08 14:17 UTCEPSS rescore
  32. 2026-06-07 23:57 UTCGHSA enrichment
  33. 2026-06-07 15:25 UTCEPSS rescore
  34. 2026-06-07 15:25 UTCEPSS rescore
  35. 2026-06-06 21:41 UTCGHSA enrichment
  36. 2026-06-06 13:47 UTCEPSS rescore
  37. 2026-06-06 13:47 UTCEPSS rescore
  38. 2026-06-05 22:47 UTCEPSS rescore
  39. 2026-06-05 19:25 UTCGHSA enrichment
  40. 2026-06-05 06:10 UTCEPSS rescore
  41. 2026-06-05 06:10 UTCEPSS rescore
  42. 2026-06-04 17:09 UTCGHSA enrichment
  43. 2026-06-04 13:12 UTCEPSS rescore
  44. 2026-06-04 13:12 UTCEPSS rescore
  45. 2026-06-03 14:52 UTCGHSA enrichment
  46. 2026-06-02 20:13 UTCEPSS rescore
  47. 2026-06-02 12:36 UTCGHSA enrichment
  48. 2026-06-01 13:52 UTCEPSS rescore
  49. 2026-06-01 13:52 UTCEPSS rescore
  50. 2026-06-01 10:20 UTCGHSA enrichment
  51. 2026-05-31 22:30 UTCEPSS rescore
  52. 2026-05-31 22:30 UTCEPSS rescore
  53. 2026-05-31 00:16 UTCEPSS rescore
  54. 2026-05-31 00:16 UTCEPSS rescore
  55. 2026-05-29 13:44 UTCEPSS rescore
  56. 2026-05-29 13:44 UTCEPSS rescore
  57. 2026-05-28 13:44 UTCEPSS rescore
  58. 2026-05-28 13:44 UTCEPSS rescore
  59. 2026-05-27 13:40 UTCEPSS rescore
  60. 2026-05-27 13:40 UTCEPSS rescore
  61. 2026-05-26 13:44 UTCEPSS rescore
  62. 2026-05-26 07:18 UTCEPSS rescore
  63. 2026-05-20 22:38 UTCEPSS rescore
  64. 2026-05-20 22:38 UTCEPSS rescore
  65. 2026-05-20 14:50 UTCEG score recompute
  66. 2026-05-20 14:50 UTCGHSA enrichment
  67. 2026-05-20 11:22 UTCEPSS rescore
  68. 2026-05-20 11:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43041?
CVE-2026-43041 is a medium vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: net: qrtr: replace qrtrtxflow radix_tree with xarray to fix memory leak radixtreecreate() allocates and links intermediate nodes into the tree one by one. If a subsequent allocation fails, the already-linked nodes remain in the…
When was CVE-2026-43041 disclosed?
CVE-2026-43041 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43041 actively exploited?
CVE-2026-43041 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.2% of all scored CVEs.
What is the CVSS score of CVE-2026-43041?
CVE-2026-43041 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-43041?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43041, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-43041

Explore →

Is Your Infrastructure Affected by CVE-2026-43041?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.