CVE-2026-93240

Published: Set 24, 2026 Last Modified: Set 25, 2026
ExploitDB:
Other exploit source:
Google Dorks:

Description

AI Translation Available

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.

https://git.kernel.org/stable/c/0a90e268cce7023f34087bfa4affb42e29ff5f45
https://git.kernel.org/stable/c/5ec8f629a300cc40e746d6178f724bdff7683fa7
https://git.kernel.org/stable/c/72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203
https://git.kernel.org/stable/c/a3417097fb107cea3358b19bcbb4eb655fd67f8c