CVE-2026-72176

mm/damon/sysfs-schemes: put stats for scheme_add_dirs() internal error

N/A
Published: August 15, 2026 at 05:53 AM UTC
Updated: August 17, 2026 at 06:18 AM 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
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: mm/damon/sysfs-schemes: put stats for scheme_add_dirs() internal error damon_sysfs_scheme_add_dirs() setup the tried_regions directory after the stats directory setup is completed. When the tried_regions directory setup is failed, the setup function ensures the reference for the tried regions directory is released. Hence the error path should put references on setup succeeded directory objects, starting from the stats directory. However, the error path is putting the tried_regions directory instead of the stats directory. As a direct result, the stats directory object is leaked. Worse yet, if the tried_regions directory setup failed from the initial allocation, the scheme->tried_regions field remains uninitialized. The following kobject_put(&scheme->tried_regions->kobj) call in the error path will dereference the uninitialized memory. The setup failures should not be common. But once it happens, the consequence is quite bad. Fix this issue by correctly putting the stats directory instead of the tried_regions directory. The issue was discovered [1] by Sashiko.

Affected

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

6.2 ≤ v < 6.12.976.2 ≤ v < 6.18.406.2 ≤ v < 6.6.1456.2 ≤ v < 7.1.56.2 ≤ v < 7.25181b75f438d2e5b7f27bf48c6ea88a87c2882b76.2
Vendor states this is fixed in 05ea83ee88ca70f8932906d9f2617ff996f45b50 (fixed)
Vendor states this is fixed in 40a04601a3f66cabd6629c258a07af645a658865 (fixed)
Vendor states this is fixed in 50a753171d255895e5dd41566986b48dcec06f31 (fixed)
Vendor states this is fixed in 6b6b5d7c2c957136b92c00b77b7175259f13082b (fixed)
Vendor states this is fixed in f63d6e5ba72aeacdee4fddc902bd7616cd62b919 (fixed)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.2 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

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