samples/damon/mtier: handle damon_stop() failure
Summary
| CVE | CVE-2026-90006 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-16 11:17:13 UTC |
| Updated | 2026-09-16 11:17:13 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
samples/damon/mtier: handle damon_stop() failure
damon_sample_mtier_stop() assumes its damon_stop() call will always
successfully stops the two DAMON contexts. Hence it deallocates the two
DAMON contexts after the damon_stop() call. However, if a given context
is already stopped, damon_stop() fails and returns an error while letting
the DAMON contexts that have not yet stopped keep running. This kind of
unexpected early DAMON context stops could happen due to memory allocation
failures in kdamond_fn(). Because damon_sample_mtier_stop() just
deallocates all DAMON contexts with damon_target and damon_region objects
that are linked to the contexts, the execution of the unstopped DAMON
context (kdamond) ends up using the memory that freed (use-after-free).
Fix the issue by separating the damon_stop() to be invoked per context.
Note that DAMON_SYSFS also allows multiple DAMON contexts execution. But,
it calls damon_stop() for each context one by one. Hence this issue is
only in mtier.
For the long term, it would be better to refactor damon_stop() to always
ensure stopping all contexts regardless of the failures in the middle.
Make this fix in the current way, though, to keep it simple and easy to
backport. I will do the refactoring later.
The issue was discovered [1] by Sashiko. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 82a08bde3cf7bbbe90de57baa181bebf676582c7 3c07c57b894116ae26f01b84c68e68b538ada7ed git |
Not specified |
| CNA |
Linux |
Linux |
affected 82a08bde3cf7bbbe90de57baa181bebf676582c7 215f9a7e4f1dcfc05ebcdc5c1ad0ea0dcb47bd09 git |
Not specified |
| CNA |
Linux |
Linux |
affected 82a08bde3cf7bbbe90de57baa181bebf676582c7 9dc5b6d66fd51b103eff21ed0df3e292f489ebc0 git |
Not specified |
| CNA |
Linux |
Linux |
affected 6.16 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.16 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.51 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.5 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/215f9a7e4f1dcfc05ebcdc5c1ad0ea0dcb47bd09 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/9dc5b6d66fd51b103eff21ed0df3e292f489ebc0 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/3c07c57b894116ae26f01b84c68e68b538ada7ed |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.