mm/damon/core: validate ranges in damon_set_regions()
Summary
| CVE | CVE-2026-68165 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-08-10 13:20:02 UTC |
| Updated | 2026-08-19 17:20:33 UTC |
| 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. |
Risk And Classification
EPSS: 0.002000000 probability, percentile 0.101970000 (date 2026-08-19)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 43b0536cb4710e7bb591edfda7e68a1c327a3409 71cf8a3ee1c18cfa8b88cc14bac9c2f43dd29f9b git | Not specified |
| CNA | Linux | Linux | affected 43b0536cb4710e7bb591edfda7e68a1c327a3409 b585facbafbb5cf117b37b1c75819ac046646c27 git | Not specified |
| CNA | Linux | Linux | affected 43b0536cb4710e7bb591edfda7e68a1c327a3409 c927b73a5694c735314ea10e7c81c07f9bd51ad7 git | Not specified |
| CNA | Linux | Linux | affected 43b0536cb4710e7bb591edfda7e68a1c327a3409 4b6f1d6d5d07855bd1bb9e64922b049062138bfa git | Not specified |
| CNA | Linux | Linux | affected 43b0536cb4710e7bb591edfda7e68a1c327a3409 43aaddd0fa92010a68adeda7744c7cf497a1c8e9 git | Not specified |
| CNA | Linux | Linux | affected 43b0536cb4710e7bb591edfda7e68a1c327a3409 1292c0ecb1caefb8ca064a3639d5673991e8810c git | Not specified |
| CNA | Linux | Linux | affected 5.16 | Not specified |
| CNA | Linux | Linux | unaffected 5.16 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.1.183 6.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.148 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.101 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.42 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.6 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/71cf8a3ee1c18cfa8b88cc14bac9c2f43dd29f9b | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/43aaddd0fa92010a68adeda7744c7cf497a1c8e9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/b585facbafbb5cf117b37b1c75819ac046646c27 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/4b6f1d6d5d07855bd1bb9e64922b049062138bfa | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/1292c0ecb1caefb8ca064a3639d5673991e8810c | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/c927b73a5694c735314ea10e7c81c07f9bd51ad7 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.