CVE-2026-68164
CVE CVE-2026-68164EUVD EUVD-2026-55550Published 2026-08-10T11:59:31.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 97d482f4592fde2322c319f07bc54f3a0d37861c <06a4beeeec8f03f0b3e9c78a98f1ae4f0f18cfbd; patch: 6.6.148; 97d482f4592fde2322c319f07bc54f3a0d37861c <954157679ec34661c2e87e7eb796104a797c32db; patch: 6.12.101; patch: 7.2-rc5; patch: 6.18.42; patch: 7.1.6; patch: 0; 97d482f4592fde2322c319f07bc54f3a0d37861c <4b4a3e7ef7bb622237495db9ba4dfd7417d6530e; 97d482f4592fde2322c319f07bc54f3a0d37861c <6ce0db97fb37ab8cf8596edca0e3de8618ab009a; 97d482f4592fde2322c319f07bc54f3a0d37861c <e33adf96afb5883f84b0d98747976bde293e33cb; 5.19
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.