CVE-2026-89752mm: memcg: stop reclaim when a limit update is superseded
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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. 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
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 19, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f before ebf762a393630d1582645be3f0fc22a674eb9122; from b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f before 4ea0617b9e46d26c0a3e5af00308ea1931cc545d; from b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f before 5c6f87d33733d96fba66ea4e78cd8b24b4d60a49; from b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f before 8bf21ad3657305e28deafd9ef16a121407496bc3; from b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f before 39ec1e4183a718f448b2e9de681dcbdda18fce42; from b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f before 95d87030cae7764805aa7c621c52871139297cb0; from b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f before aab391074de96ed601eeca32daef9a8507d436d9; from b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f before 9477820c63cbf4d97114238f3d1ff10dfd6bee3f; and 4 more ranges | CNA record |
References
- https://git.kernel.org/stable/c/ebf762a393630d1582645be3f0fc22a674eb9122
- 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/39ec1e4183a718f448b2e9de681dcbdda18fce42
- https://git.kernel.org/stable/c/95d87030cae7764805aa7c621c52871139297cb0
- https://git.kernel.org/stable/c/aab391074de96ed601eeca32daef9a8507d436d9
- https://git.kernel.org/stable/c/9477820c63cbf4d97114238f3d1ff10dfd6bee3f
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.