CVE-2026-64239

mm/damon/sysfs-schemes: delete tried region in regions_rmdirs()

HIGH
7.8
CVSS Score
Published: July 24, 2026 at 03:27 PM UTC
Updated: August 13, 2026 at 05:37 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: mm/damon/sysfs-schemes: delete tried region in regions_rmdirs() DAMON sysfs maintains the DAMOS tried region directory objects via a linked list. When the user requests refresh of the directories, DAMON sysfs removes all the region directories first, and then generate updated regions directory on the empty space. The removal function (damon_sysfs_scheme_regions_rm_dirs()) only puts the kobj objects. Deletion of the container region object from the linked list is done inside the kobj release callback function. If somehow the callback invocation is delayed, the list will contain regions list that gonna be freed. If the updated region directories creation is started in this situation, the list can be corrupted and use-after-free can happen. Because the kobj objects are managed by only DAMON sysfs, the issue cannot happen in normal situation. But, such delays can be made on kernels that built with CONFIG_DEBUG_KOBJECT_RELEASE. On the kernel, the issue can indeed be reproduced like below. # damo start --damos_action stat # cd /sys/kernel/mm/damon/admin/kdamonds/0/ # for i in {1..10}; do echo update_schemes_tried_regions > state; done # dmesg | grep underflow [ 89.296152] refcount_t: underflow; use-after-free. Fix the issue by removing the region object from the list when decrementing the reference count. Also update damos_sysfs_populate_region_dir() to add the region object to the list only after the kobject_init_and_add() is success, so that fail of kobject_init_and_add() is not leaving the deallocated object on the list. The issue was discovered [1] by Sashiko.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.13 ≤ v < 6.18.356.19 ≤ v < 7.0.126.2 ≤ v < 6.12.936.2 ≤ v < 6.18.356.2 ≤ v < 6.6.1436.2 ≤ v < 7.0.126.2 ≤ v < 7.16.7 ≤ v < 6.12.937.1 rc17.1 rc27.1 rc37.1 rc47.1 rc59277d0367ba18ef4bb98bafb1209e715844cdf7e
Vendor states this is fixed in 0ba6c05156d9ff9fc6ca22b7690e2eec9eca66f7 (fixed)
Vendor states this is fixed in 2c33177023c92e76806c535ddbffaa3d3fc37777 (fixed)
Vendor states this is fixed in 441f92f7d386b85bad16de49db95a307cba048a2 (fixed)
Vendor states this is fixed in a5fa42214de55e43d165144727ce9facb9fc6b08 (fixed)
Vendor states this is fixed in c0e37017a452addec873865c94cf7a665663a9b2 (fixed)
Vendor states this is fixed in 6.12.93 (unaffected)
Vendor states this is fixed in 6.18.35 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)
Vendor states this is fixed in 6.6.143 (unaffected)
Vendor states this is fixed in 7.0.12 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-416

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card