CVE-2026-90006
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().
Leer descripción completaMostrar menos
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.
CVSS
NVD no ha asignado puntuación CVSS a esta CVE (habitual desde el cambio de política de abril de 2026).
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.22%
- Percentil entre todas las CVEs puntuadas: 12
- Fecha de la puntuación: 6/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
Tecnologías afectadas (1)
⚠ Inferidas por IA a partir de la descripción — NVD aún no ha analizado esta CVE; no son CPE verificados.
Referencias
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-90006",
"cveTags": [],
"metrics": {},
"affected": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"affectedData": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "82a08bde3cf7bbbe90de57baa181bebf676582c7",
"lessThan": "3c07c57b894116ae26f01b84c68e68b538ada7ed",
"versionType": "git"
},
{
"status": "affected",
"version": "82a08bde3cf7bbbe90de57baa181bebf676582c7",
"lessThan": "215f9a7e4f1dcfc05ebcdc5c1ad0ea0dcb47bd09",
"versionType": "git"
},
{
"status": "affected",
"version": "82a08bde3cf7bbbe90de57baa181bebf676582c7",
"lessThan": "9dc5b6d66fd51b103eff21ed0df3e292f489ebc0",
"versionType": "git"
}
],
"programFiles": [
"samples/damon/mtier.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "6.16"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "6.16",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "6.18.51",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.2.5",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"samples/damon/mtier.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-09-16T11:17:13.213",
"references": [
{
"url": "https://git.kernel.org/stable/c/215f9a7e4f1dcfc05ebcdc5c1ad0ea0dcb47bd09",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/3c07c57b894116ae26f01b84c68e68b538ada7ed",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/9dc5b6d66fd51b103eff21ed0df3e292f489ebc0",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nsamples/damon/mtier: handle damon_stop() failure\n\ndamon_sample_mtier_stop() assumes its damon_stop() call will always\nsuccessfully stops the two DAMON contexts. Hence it deallocates the two\nDAMON contexts after the damon_stop() call. However, if a given context\nis already stopped, damon_stop() fails and returns an error while letting\nthe DAMON contexts that have not yet stopped keep running. This kind of\nunexpected early DAMON context stops could happen due to memory allocation\nfailures in kdamond_fn(). Because damon_sample_mtier_stop() just\ndeallocates all DAMON contexts with damon_target and damon_region objects\nthat are linked to the contexts, the execution of the unstopped DAMON\ncontext (kdamond) ends up using the memory that freed (use-after-free). \nFix the issue by separating the damon_stop() to be invoked per context.\n\nNote that DAMON_SYSFS also allows multiple DAMON contexts execution. But,\nit calls damon_stop() for each context one by one. Hence this issue is\nonly in mtier.\n\nFor the long term, it would be better to refactor damon_stop() to always\nensure stopping all contexts regardless of the failures in the middle. \nMake this fix in the current way, though, to keep it simple and easy to\nbackport. I will do the refactoring later.\n\nThe issue was discovered [1] by Sashiko."
}
],
"lastModified": "2026-09-16T11:17:13.213",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}