CVE-2026-68164

Published: Ago 10, 2026 Last Modified: Ago 10, 2026
ExploitDB:
Other exploit source:
Google Dorks:

Description

AI Translation Available

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

mm/damon/core: disallow overlapping input ranges for damon_set_regions()

damon_set_regions() assumes the input ranges are sorted by the address and
don't overlap each other. Hence the assumption was initially to be
explicitly validated. But commit 97d482f4592f ('mm/damon/sysfs: reuse
damon_set_regions() for regions setting') has mistakenly removed the
validation.

This can make DAMON behave in unexpected ways. At the best, the
monitoring results snapshot will just look weird since there will be
overlapping regions. DAMOS will also work weirdly, applying the same
action multiple times for overlapping regions, and make DAMOS quota weird.
More seriously, depending on the setup and regions updates sequence,
negative size regions can be made. It will trigger WARN_ONCE() if the
kernel is built with CONFIG_DAMON_DEBUG_SANITY=y. Depending on the
monitoring results, the negative size region can further trigger division
by zero in damon_merge_two_regions().

Note that some of the consequences including the WARN_ONCE() and the
divide by zero depend on commits that were introduced after the root cause
commit 97d482f4592f ('mm/damon/sysfs: reuse damon_set_regions() for
regions setting').

Fix the problems by checking the assumption and returning an error if
the input ranges don't meet the assumption.

The issue was discovered [1] by Sashiko.

https://git.kernel.org/stable/c/06a4beeeec8f03f0b3e9c78a98f1ae4f0f18cfbd
https://git.kernel.org/stable/c/4b4a3e7ef7bb622237495db9ba4dfd7417d6530e
https://git.kernel.org/stable/c/6ce0db97fb37ab8cf8596edca0e3de8618ab009a
https://git.kernel.org/stable/c/954157679ec34661c2e87e7eb796104a797c32db
https://git.kernel.org/stable/c/e33adf96afb5883f84b0d98747976bde293e33cb