Answer in brief
CVE-2026-68165 records a Unknown severity vulnerability in mm/damon/core: validate ranges in damon_set_regions(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=43b0536cb4710e7bb591edfda7e68a1c327a3409 <b585facbafbb5cf117b37b1c75819ac046646c27 || >=43b0536cb4710e7bb591edfda7e68a1c327a3409 <c927b73a5694c735314ea10e7c81c07f9bd51ad7 || >=43b0536cb4710e7bb591edfda7e68a1c327a3409 <4b6f1d6d5d07855bd1bb9e64922b049062138bfa || >=43b0536cb4710e7bb591edfda7e68a1c327a3409 <43aaddd0fa92010a68adeda7744c7cf497a1c8e9 || >=43b0536cb4710e7bb591edfda7e68a1c327a3409 <1292c0ecb1caefb8ca064a3639d5673991e8810c | b585facbafbb5cf117b37b1c75819ac046646c27, c927b73a5694c735314ea10e7c81c07f9bd51ad7, 4b6f1d6d5d07855bd1bb9e64922b049062138bfa, 43aaddd0fa92010a68adeda7744c7cf497a1c8e9, 1292c0ecb1caefb8ca064a3639d5673991e8810c |
| Linux/Linuxgeneric | 5.16 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68165 records a Unknown severity vulnerability in mm/damon/core: validate ranges in damon_set_regions(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=43b0536cb4710e7bb591edfda7e68a1c327a3409 <b585facbafbb5cf117b37b1c75819ac046646c27 || >=43b0536cb4710e7bb591edfda7e68a1c327a3409 <c927b73a5694c735314ea10e7c81c07f9bd51ad7 || >=43b0536cb4710e7bb591edfda7e68a1c327a3409 <4b6f1d6d5d07855bd1bb9e64922b049062138bfa || >=43b0536cb4710e7bb591edfda7e68a1c327a3409 <43aaddd0fa92010a68adeda7744c7cf497a1c8e9 || >=43b0536cb4710e7bb591edfda7e68a1c327a3409 <1292c0ecb1caefb8ca064a3639d5673991e8810c | b585facbafbb5cf117b37b1c75819ac046646c27, c927b73a5694c735314ea10e7c81c07f9bd51ad7, 4b6f1d6d5d07855bd1bb9e64922b049062138bfa, 43aaddd0fa92010a68adeda7744c7cf497a1c8e9, 1292c0ecb1caefb8ca064a3639d5673991e8810c |
| Linux/Linuxgeneric | 5.16 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.