CVE Catalog

CVE-2026-93240

Low risk· EPSS 11%
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.22%

11th percentile - higher than 11% of all known CVEs

Summary

In the Linux kernel, the memcg v1 soft limit has been deprecated — writes to memory.soft_limit_in_bytes are now ignored and reads always report the maximum value. The fix also addresses a syzbot warning related to soft limit reclaim invoked from kswapd.

Risk Assessment

Organizations relying on memcg v1 soft limit may observe changed memory limiting behavior, potentially affecting predictability of memory management in containers.

Recommendation

Update the Linux kernel to a version with the fix and verify that workloads do not depend on the deprecated memcg v1 soft limit mechanism. Consider migrating to cgroup v2 mechanisms.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: memcg: make the v1 soft limit knob inert The v1 soft limit has been deprecated since v6.12 and nobody has reported depending on it. Start the removal by decoupling the interface from the implementation: keep memory.soft_limit_in_bytes, but ignore writes to it and always report the maximum value on read similar to what memory.kmem.limit_in_bytes already does. Writes are still parsed, so malformed input keeps returning -EINVAL. The knob now also behaves the same everywhere: it used to return -EOPNOTSUPP on PREEMPT_RT, where soft limit reclaim has always been disabled. This also fixes the syzbot report linked below. Soft limit reclaim is the only caller that runs shrink_lruvec() from kswapd against a specific memcg, so it is the only way to reach lru_gen_shrink_lruvec() and in turn set_mm_walk(), which warns when called from kswapd.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS