CVE-2026-68165mm/damon/core: validate ranges in damon_set_regions()
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 11 days later
· 11 days later
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.21% · top 88% of all CVEs (17 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 43b0536cb4710e7bb591edfda7e68a1c327a3409 – < 71cf8a3ee1c18cfa8b88cc14bac9c2f43dd29f9b
- affected 43b0536cb4710e7bb591edfda7e68a1c327a3409 – < b585facbafbb5cf117b37b1c75819ac046646c27
- affected 43b0536cb4710e7bb591edfda7e68a1c327a3409 – < c927b73a5694c735314ea10e7c81c07f9bd51ad7
- affected 43b0536cb4710e7bb591edfda7e68a1c327a3409 – < 4b6f1d6d5d07855bd1bb9e64922b049062138bfa
- affected 43b0536cb4710e7bb591edfda7e68a1c327a3409 – < 43aaddd0fa92010a68adeda7744c7cf497a1c8e9
- affected 43b0536cb4710e7bb591edfda7e68a1c327a3409 – < 1292c0ecb1caefb8ca064a3639d5673991e8810c
- affected 5.16
- unaffected < 5.16
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.148 – ≤ 6.6.*
- unaffected 6.12.101 – ≤ 6.12.*
- unaffected 6.18.42 – ≤ 6.18.*
- unaffected 7.1.6 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/71cf8a3ee1c18cfa8b88cc14bac9c2f43dd29f9b (opens in a new tab)
- https://git.kernel.org/stable/c/b585facbafbb5cf117b37b1c75819ac046646c27 (opens in a new tab)
- https://git.kernel.org/stable/c/c927b73a5694c735314ea10e7c81c07f9bd51ad7 (opens in a new tab)
- https://git.kernel.org/stable/c/4b6f1d6d5d07855bd1bb9e64922b049062138bfa (opens in a new tab)
- https://git.kernel.org/stable/c/43aaddd0fa92010a68adeda7744c7cf497a1c8e9 (opens in a new tab)
- https://git.kernel.org/stable/c/1292c0ecb1caefb8ca064a3639d5673991e8810c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-55551 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-68165)Record last updated .