CVE-2026-72176
In the Linux kernel, the following vulnerability has been resolved: …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/05ea83ee88ca70f8932906d9f2617ff996f45b50
- git.kernel.org/stable/c/40a04601a3f66cabd6629c258a07af645a658865
- git.kernel.org/stable/c/50a753171d255895e5dd41566986b48dcec06f31
- git.kernel.org/stable/c/6b6b5d7c2c957136b92c00b77b7175259f13082b
- git.kernel.org/stable/c/f63d6e5ba72aeacdee4fddc902bd7616cd62b919
- nvd.nist.gov/vuln/detail/CVE-2026-72176
- cve.org/CVERecord?id=CVE-2026-72176
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.