Linux Kernel up to 7.2-rc4 DAMON Core mm/damon/core.c damon_set_regions divide by zero

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
3.0$0-$5k0.53+

Summaryinfo

A vulnerability labeled as problematic has been found in Linux Kernel up to 6.6.147/6.12.100/6.18.41/7.1.5/7.2-rc4. This affects the function damon_set_regions of the file mm/damon/core.c of the component DAMON Core. The manipulation results in divide by zero. This vulnerability is identified as CVE-2026-68165. The attack is only possible with local access. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Linux Kernel up to 6.6.147/6.12.100/6.18.41/7.1.5/7.2-rc4. Affected is the function damon_set_regions of the file mm/damon/core.c of the component DAMON Core. The manipulation with an unknown input leads to a divide by zero vulnerability. CWE is classifying the issue as CWE-369. The product divides a value by zero. This is going to have an impact on integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2026-68165 since 07/30/2026. The exploitability is told to be easy. The attack needs to be approached locally. The exploitation needs additional levels of successful authentication. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.

Upgrading to version 6.6.148, 6.12.101, 6.18.42, 7.1.6 or 7.2-rc5 eliminates this vulnerability. Applying the patch b585facbafbb5cf117b37b1c75819ac046646c27/c927b73a5694c735314ea10e7c81c07f9bd51ad7/4b6f1d6d5d07855bd1bb9e64922b049062138bfa/43aaddd0fa92010a68adeda7744c7cf497a1c8e9/1292c0ecb1caefb8ca064a3639d5673991e8810c is able to eliminate this problem.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 3.1
VulDB Meta Temp Score: 3.0

VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Divide by zero
CWE: CWE-369 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: Partially

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.148/6.12.101/6.18.42/7.1.6/7.2-rc5
Patch: b585facbafbb5cf117b37b1c75819ac046646c27/c927b73a5694c735314ea10e7c81c07f9bd51ad7/4b6f1d6d5d07855bd1bb9e64922b049062138bfa/43aaddd0fa92010a68adeda7744c7cf497a1c8e9/1292c0ecb1caefb8ca064a3639d5673991e8810c

Timelineinfo

07/30/2026 CVE reserved
08/10/2026 +11 days Advisory disclosed
08/10/2026 +0 days VulDB entry created
08/10/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-68165 (🔒)
GCVE (CVE): GCVE-0-2026-68165
GCVE (VulDB): GCVE-100-387516

Entryinfo

Created: 08/10/2026 15:38
Changes: 08/10/2026 15:38 (60)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!