CVE-2026-89752
In the Linux kernel, the following vulnerability has been resolved:
mm: memcg: stop reclaim when a limit update is superseded
kernfs serializes file operations only per open file, so separate open files can update the same memory.high or memory.max file concurrently. Both handlers store the new limit before synchronous reclaim, but continue to use the writer's local target in the reclaim loop. If another writer raises or removes the limit, the first writer can continue reclaiming toward a stale target.
For memory.max, this can leave the writer looping indefinitely once reclaim retries are exhausted.
Leer descripción completaMostrar menos
The OOM path sees sufficient margin under the current limit and returns true without killing, while the writer still compares usage against its stale target and records another OOM event.
Check the current limit at the start of each reclaim iteration and stop if it no longer matches the writer's target.
Reproducer:
Populate a cgroup with anonymous memory and disable swapping. Lower memory.max from one open file, then restore it to "max" through another open file after the new limit becomes visible.
Without the patch, the first writer remains blocked and repeatedly increments the OOM event counter. With the patch, it returns normally.
This was not motivated by a reported production workload. We found it through automated randomized testing for our cgroup observability work and reduced it to the reproducer above.
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: 11
- Fecha de la puntuación: 3/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
- https://git.kernel.org/stable/c/39ec1e4183a718f448b2e9de681dcbdda18fce42
- https://git.kernel.org/stable/c/4ea0617b9e46d26c0a3e5af00308ea1931cc545d
- https://git.kernel.org/stable/c/5c6f87d33733d96fba66ea4e78cd8b24b4d60a49
- https://git.kernel.org/stable/c/8bf21ad3657305e28deafd9ef16a121407496bc3
- https://git.kernel.org/stable/c/9477820c63cbf4d97114238f3d1ff10dfd6bee3f
- https://git.kernel.org/stable/c/95d87030cae7764805aa7c621c52871139297cb0
- https://git.kernel.org/stable/c/aab391074de96ed601eeca32daef9a8507d436d9
- https://git.kernel.org/stable/c/ebf762a393630d1582645be3f0fc22a674eb9122
JSON original (NVD)
Mostrar
{
"id": "CVE-2026-89752",
"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": "b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f",
"lessThan": "ebf762a393630d1582645be3f0fc22a674eb9122",
"versionType": "git"
},
{
"status": "affected",
"version": "b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f",
"lessThan": "4ea0617b9e46d26c0a3e5af00308ea1931cc545d",
"versionType": "git"
},
{
"status": "affected",
"version": "b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f",
"lessThan": "5c6f87d33733d96fba66ea4e78cd8b24b4d60a49",
"versionType": "git"
},
{
"status": "affected",
"version": "b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f",
"lessThan": "8bf21ad3657305e28deafd9ef16a121407496bc3",
"versionType": "git"
},
{
"status": "affected",
"version": "b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f",
"lessThan": "39ec1e4183a718f448b2e9de681dcbdda18fce42",
"versionType": "git"
},
{
"status": "affected",
"version": "b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f",
"lessThan": "95d87030cae7764805aa7c621c52871139297cb0",
"versionType": "git"
},
{
"status": "affected",
"version": "b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f",
"lessThan": "aab391074de96ed601eeca32daef9a8507d436d9",
"versionType": "git"
},
{
"status": "affected",
"version": "b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f",
"lessThan": "9477820c63cbf4d97114238f3d1ff10dfd6bee3f",
"versionType": "git"
},
{
"status": "affected",
"version": "0ccab5b139971a2a3f48df24d1ee8be2dbf84042",
"versionType": "git"
},
{
"status": "affected",
"version": "97729c37439040ec07807f0dbb71ea60ccbafd27",
"versionType": "git"
},
{
"status": "affected",
"version": "4.4.7",
"lessThan": "4.5",
"versionType": "semver"
},
{
"status": "affected",
"version": "4.5.1",
"lessThan": "4.6",
"versionType": "semver"
}
],
"programFiles": [
"mm/memcontrol.c"
],
"defaultStatus": "unaffected"
},
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"product": "Linux",
"versions": [
{
"status": "affected",
"version": "4.6"
},
{
"status": "unaffected",
"version": "0",
"lessThan": "4.6",
"versionType": "semver"
},
{
"status": "unaffected",
"version": "5.10.270",
"versionType": "semver",
"lessThanOrEqual": "5.10.*"
},
{
"status": "unaffected",
"version": "5.15.221",
"versionType": "semver",
"lessThanOrEqual": "5.15.*"
},
{
"status": "unaffected",
"version": "6.1.188",
"versionType": "semver",
"lessThanOrEqual": "6.1.*"
},
{
"status": "unaffected",
"version": "6.6.157",
"versionType": "semver",
"lessThanOrEqual": "6.6.*"
},
{
"status": "unaffected",
"version": "6.12.109",
"versionType": "semver",
"lessThanOrEqual": "6.12.*"
},
{
"status": "unaffected",
"version": "6.18.50",
"versionType": "semver",
"lessThanOrEqual": "6.18.*"
},
{
"status": "unaffected",
"version": "7.2.4",
"versionType": "semver",
"lessThanOrEqual": "7.2.*"
},
{
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix",
"lessThanOrEqual": "*"
}
],
"programFiles": [
"mm/memcontrol.c"
],
"defaultStatus": "affected"
}
]
}
],
"published": "2026-09-11T20:20:06.123",
"references": [
{
"url": "https://git.kernel.org/stable/c/39ec1e4183a718f448b2e9de681dcbdda18fce42",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/4ea0617b9e46d26c0a3e5af00308ea1931cc545d",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/5c6f87d33733d96fba66ea4e78cd8b24b4d60a49",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/8bf21ad3657305e28deafd9ef16a121407496bc3",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/9477820c63cbf4d97114238f3d1ff10dfd6bee3f",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/95d87030cae7764805aa7c621c52871139297cb0",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/aab391074de96ed601eeca32daef9a8507d436d9",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
},
{
"url": "https://git.kernel.org/stable/c/ebf762a393630d1582645be3f0fc22a674eb9122",
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"vulnStatus": "Received",
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nmm: memcg: stop reclaim when a limit update is superseded\n\nkernfs serializes file operations only per open file, so separate open\nfiles can update the same memory.high or memory.max file concurrently. \nBoth handlers store the new limit before synchronous reclaim, but continue\nto use the writer's local target in the reclaim loop. If another writer\nraises or removes the limit, the first writer can continue reclaiming\ntoward a stale target.\n\nFor memory.max, this can leave the writer looping indefinitely once\nreclaim retries are exhausted. The OOM path sees sufficient margin under\nthe current limit and returns true without killing, while the writer still\ncompares usage against its stale target and records another OOM event.\n\nCheck the current limit at the start of each reclaim iteration and stop if\nit no longer matches the writer's target.\n\nReproducer:\n\nPopulate a cgroup with anonymous memory and disable swapping. Lower\nmemory.max from one open file, then restore it to \"max\" through another\nopen file after the new limit becomes visible.\n\nWithout the patch, the first writer remains blocked and repeatedly\nincrements the OOM event counter. With the patch, it returns normally.\n\nThis was not motivated by a reported production workload. We found it\nthrough automated randomized testing for our cgroup observability work\nand reduced it to the reproducer above."
}
],
"lastModified": "2026-09-14T13:19:23.897",
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}