CVE-2026-89752

CVE CVE-2026-89752EUVD EUVD-2026-76664Published 2026-09-11T19:46:56.000ZLast changed 2026-09-14T12:02:32.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 0ccab5b139971a2a3f48df24d1ee8be2dbf84042; b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f <4ea0617b9e46d26c0a3e5af00308ea1931cc545d; patch: 5.15.221; b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f <ebf762a393630d1582645be3f0fc22a674eb9122; patch: 6.1.188; 97729c37439040ec07807f0dbb71ea60ccbafd27; 4.6; b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f <9477820c63cbf4d97114238f3d1ff10dfd6bee3f; b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f <8bf21ad3657305e28deafd9ef16a121407496bc3; patch: 6.18.50; 4.5.1 <4.6; 4.4.7 <4.5; patch: 6.12.109; patch: 7.2.4; b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f <5c6f87d33733d96fba66ea4e78cd8b24b4d60a49; b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f <95d87030cae7764805aa7c621c52871139297cb0; patch: 6.6.157; patch: 7.3-rc1; patch: 5.10.270; b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f <aab391074de96ed601eeca32daef9a8507d436d9; patch: 0; b6e6edcfa40561e9c8abe5eecf1c96f8e5fd9c6f <39ec1e4183a718f448b2e9de681dcbdda18fce42

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.