CVE-2026-52905

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-09. 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/core: disallow non-power of two min_region_sz on damon_start()

Commit d8f867fa0825 ("mm/damon: add damon_ctx->min_sz_region") introduced a bug that allows unaligned DAMON region address ranges. Commit c80f46ac228b ("mm/damon/core: disallow non-power of two min_region_sz") fixed it, but only for damon_commit_ctx() use case. Still, DAMON sysfs interface can emit non-power of two min_region_sz via damon_start(). Fix the path by adding the is_power_of_2() check on damon_start().

The issue was discovered by sashiko [1].

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

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (3)

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

mm/damon/core: disallow non-power of two min_region_sz on damon_start() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/95093e5cb4c5b50a5b1a4b79f2942b62744bd66a
generic

mm/damon/core: disallow non-power of two min_region_sz on damon_start() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/89b6226b6c2a4add3939f361653a47c212d6ab75
generic

mm/damon/core: disallow non-power of two min_region_sz on damon_start() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1de2db19a6028abe7d905875922faef5b873de67

Vendor Advisories for CVE-2026-52905(1)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-09-14ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-09-14ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-09-14ubuntu

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.4-1~bpo13+1 (134 versions)7.0.4-1—

Weakness Classification(1)

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

All Vendor Advisories

(6)

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 6× in last 7d / 35× 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 202 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-52905?
CVE-2026-52905 is a medium vulnerability published on June 9, 2026. In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: disallow non-power of two minregionsz on damon_start() Commit d8f867fa0825 ("mm/damon: add damonctx->minsz_region") introduced a bug that allows unaligned DAMON region address ranges. Commit c80f46ac228b…
When was CVE-2026-52905 disclosed?
CVE-2026-52905 was first published in the National Vulnerability Database on June 9, 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-52905 actively exploited?
CVE-2026-52905 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.4% of all scored CVEs.
What is the CVSS score of CVE-2026-52905?
CVE-2026-52905 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-52905?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52905, 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-52905

Explore →

Is Your Infrastructure Affected by CVE-2026-52905?

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

Start Free Scan →Browse All CVEs