mm/damon/core: disallow overlapping input ranges for damon_set_regions()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel e33adf96afb5883f84b0d98747976bde293e33cb, Kernel 06a4beeeec8f03f0b3e9c78a98f1ae4f0f18cfbd, Kernel 4b4a3e7ef7bb622237495db9ba4dfd7417d6530e and 8 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=97d482f4592fde2322c319f07bc54f3a0d37861c <e33adf96afb5883f84b0d98747976bde293e33cb, >=97d482f4592fde2322c319f07bc54f3a0d37861c <06a4beeeec8f03f0b3e9c78a98f1ae4f0f18cfbd, >=97d482f4592fde2322c319f07bc54f3a0d37861c <4b4a3e7ef7bb622237495db9ba4dfd7417d6530e, >=97d482f4592fde2322c319f07bc54f3a0d37861c <6ce0db97fb37ab8cf8596edca0e3de8618ab009a, >=97d482f4592fde2322c319f07bc54f3a0d37861c <954157679ec34661c2e87e7eb796104a797c32db, >=97d482f4592fde2322c319f07bc54f3a0d37861c <a5c453fffb6f2ce75fc10b5d8bc475f1758010bd, =5.19 | e33adf96afb5883f84b0d98747976bde293e33cb, 06a4beeeec8f03f0b3e9c78a98f1ae4f0f18cfbd, 4b4a3e7ef7bb622237495db9ba4dfd7417d6530e, 6ce0db97fb37ab8cf8596edca0e3de8618ab009a, 954157679ec34661c2e87e7eb796104a797c32db, a5c453fffb6f2ce75fc10b5d8bc475f1758010bd |
| linux-kernel: Kernel | >=6.13.0 <6.18.42, >=6.19.0 <7.1.6, >=6.2.0 <6.6.148, >=6.7.0 <6.12.101, >=5.19.0 <6.1.183 | 6.18.42, 7.1.6, 6.6.148, 6.12.101, 6.1.183 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket