CVE-2026-89752

A flaw was found in the Linux kernel's memory cgroup memcg component. When multiple file operations concurrently update memory.high or memory.max files in kernfs, a writer can continue reclaiming memory towards an outdated target. This can lead to an indefinite loop, causing a denial of service D...

DEBIAN-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...

UBUNTU-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...

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...

CVE-2026-89752

A race condition in the Linux kernel's memory cgroup (memcg) subsystem can cause an indefinite reclaim loop when two open files concurrently update memory.max or memory.high. Because kernfs serializes operations only per open file, a first writer may continue reclaiming toward a stale target afte...

CVE-2026-89752: Undefined Security Weakness

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...

kernel: memcg: OOM handling DoS

It was found that the Linux kernel memory resource controller's memcg handling of OOM out of memory conditions could lead to deadlocks. An attacker able to continuously spawn new processes within a single memory-constrained cgroup during an OOM event could use this flaw to lock up the system...