CVE-2026-52905
Received Received - Intake
Linux Kernel DAMON Region Size Validation Flaw

Publication date: 2026-06-09

Last updated on: 2026-06-09

Assigner: kernel.org

Description
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 Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-09
Last Modified
2026-06-09
Generated
2026-06-09
AI Q&A
2026-06-09
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in the Linux kernel's DAMON (Data Access MONitor) subsystem. A recent code change introduced a bug that allows unaligned DAMON region address ranges by not properly enforcing that the minimum region size (min_region_sz) is a power of two when starting DAMON monitoring via the damon_start() function. Although a fix was applied for one use case (damon_commit_ctx()), the damon_start() path still allowed non-power of two values, which was corrected by adding a check to ensure min_region_sz is a power of two.

Impact Analysis

The vulnerability could lead to improper or unexpected behavior in the DAMON subsystem due to unaligned memory region monitoring. This might affect the accuracy or reliability of memory access monitoring, potentially causing system instability or incorrect performance data. However, no specific impacts such as privilege escalation or data leakage are described.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-52905. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart