CVE-2026-93240
In the Linux kernel, the following vulnerability has been resolved: …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/0a90e268cce7023f34087bfa4affb42e29ff5f45
- git.kernel.org/stable/c/5ec8f629a300cc40e746d6178f724bdff7683fa7
- git.kernel.org/stable/c/72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203
- git.kernel.org/stable/c/a3417097fb107cea3358b19bcbb4eb655fd67f8c
- git.kernel.org/stable/c/bf75f14d755f9cfbb246e6cc011b53cdd5142de3
- nvd.nist.gov/vuln/detail/CVE-2026-93240
- cve.org/CVERecord?id=CVE-2026-93240
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.