All reports
Low

kernel: mm/damon/core: validate ranges in damon_set_regions()

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-68165

Probability of exploitation in the next 30 days: 0.21%

FIRST EPSS · 2026-11-21

Description

In the Linux kernel, the following vulnerability has been resolved: mm/damon/core: validate ranges in damon_set_regions() DAMON core logic assumes zero length regions don't exist. However, a few DAMON API callers including DAMON_SYSFS, DAMON_RECLAIM and DAMON_LRU_SORT allow users to set empty monitoring target regions. This could result in WARN_ONCE() on CONFIG_DAMON_DEBUG_SANITY enabled kernel, and divide-by-zero from damon_merge_two_regions(). For example, the WANR_ONCE() can be triggered like below.

grep DAMON_DEBUG_SANITY /boot/config-$(uname -r)

CONFIG_DAMON_DEBUG_SANITY=y

damo start

cd /sys/kernel/mm/damon/admin/kdamonds/0

echo 0 > contexts/0/targets/0/regions/0/start

echo 0 > contexts/0/targets/0/regions/0/end

echo commit > state

dmesg

[....] [ 73.705780] ------------[ cut here ]------------ [ 73.707552] start 0 >= end 0 [ 73.708452] WARNING: mm/damon/core.c:359 at damon_new_region+0x6e/0x80, CPU#1: kdamond.0/758 [...] All DAMON API callers eventually use damon_set_regions() to setup the regions. Add the validation logic in the function.

A flaw was found in the Linux kernel's Data Access MONitor (DAMON) core logic. A local user could exploit this by providing invalid, zero-length memory region ranges through DAMON's application programming interface (API) callers. This improper input validation can lead to a divide-by-zero error, potentially causing a system crash and resulting in a Denial of Service (DoS).