cveboard RSS feed

CVE-2026-64239

CVE.org · Published

Historical CVEsJSONAI instructions

Record status
Published
Identifier year (not publication year)
2026
Source publication
Source updated
Imported by cveboard
Source snapshot
cve_2026-10-24_midnight_baseline ·

Plain text

CNA source text (English)

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

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.

Scoped product and version facts

Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.

Exploitation unknown; this catalogue does not assess exploitation.

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
unaffected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
9277d0367ba18ef4bb98bafb1209e715844cdf7eaffectedgitc0e37017a452addec873865c94cf7a665663a9b2UnavailableNone listed
9277d0367ba18ef4bb98bafb1209e715844cdf7eaffectedgita5fa42214de55e43d165144727ce9facb9fc6b08UnavailableNone listed
9277d0367ba18ef4bb98bafb1209e715844cdf7eaffectedgit0ba6c05156d9ff9fc6ca22b7690e2eec9eca66f7UnavailableNone listed
9277d0367ba18ef4bb98bafb1209e715844cdf7eaffectedgit2c33177023c92e76806c535ddbffaa3d3fc37777UnavailableNone listed
9277d0367ba18ef4bb98bafb1209e715844cdf7eaffectedgit441f92f7d386b85bad16de49db95a307cba048a2UnavailableNone listed

Linux

Vendor
Linux
Product
Linux
Platforms
Unknown
Default status
affected
Linux · Scoped product and version facts
Version (version)Status (status)Version scheme (versionType)Exclusive end (lessThan)Inclusive end (lessThanOrEqual)Status changes (at → status)
6.2affectedUnavailableUnavailableUnavailableNone listed
0unaffectedsemver6.2UnavailableNone listed
6.6.143unaffectedsemverUnavailable6.6.*None listed
6.12.93unaffectedsemverUnavailable6.12.*None listed
6.18.35unaffectedsemverUnavailable6.18.*None listed
7.0.12unaffectedsemverUnavailable7.0.*None listed
7.1unaffectedoriginal_commit_for_fixUnavailable*None listed