CVE-2026-53334

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

mm/damon/reclaim: handle ctx allocation failure

Patch series "mm/damon/{reclaim,lru_sort}: handle ctx allocation failures".

DAMON_RECLAIM and DAMON_LRU_SORT could dereference NULL pointers if their damon_ctx object allocations fail. The bugs are expected to happen infrequently because the allocations are arguably too small to fail on common setups. But theoretically they are possible and the consequences are bad. Fix those.

The issues were discovered [1] by Sashiko.

This patch (of 2):

DAMON_RECLAIM allocates the damon_ctx object for its kdamond in its init function. damon_reclaim_enabled_store() wrongly assumes the allocation will always succeed once tried. If the damon_ctx allocation was failed, therefore, code execution reaches to damon_commit_ctx() while 'ctx' is NULL. As a result, it dereferences the NULL 'ctx' pointer. Avoid the NULL dereference by returning -ENOMEM if 'ctx' is NULL.

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
7%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jul 24, 2026
No patch confirmed yet.
generic

mm/damon/reclaim: handle ctx allocation failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7e2ed8a29427af534bf2cb9b8bc51762b8b6e654
generic

mm/damon/reclaim: handle ctx allocation failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66bc00ea37fa8ec14be5a3909d067a5967ef234b
generic

mm/damon/reclaim: handle ctx allocation failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/635b45ce61de53a9357e28ac97461428cdb650f0

Vendor Advisories for CVE-2026-53334(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-12ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-12ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-12ubuntu

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.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1

Weakness Classification(1)

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

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 53× 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.

Showing the most recent 100 of 434 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53334?
CVE-2026-53334 is a medium vulnerability published on July 1, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/damon/reclaim: handle ctx allocation failure Patch series "mm/damon/{reclaim,lru_sort}: handle ctx allocation failures". DAMONRECLAIM and DAMONLRU_SORT could dereference NULL pointers if their damon_ctx object allocations fail.…
When was CVE-2026-53334 disclosed?
CVE-2026-53334 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53334 actively exploited?
CVE-2026-53334 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 93.4% of all scored CVEs.
What is the CVSS score of CVE-2026-53334?
CVE-2026-53334 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53334?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53334, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53334

Explore →

Is Your Infrastructure Affected by CVE-2026-53334?

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