CVE-2026-93240: Linux kernel · memcg: make the v1 soft limit knob inert
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in bf75f14d755f9cfbb246e6cc011b53cdd5142de3 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:18 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in bf75f14d755f9cfbb246e6cc011b53cdd5142de3, a3417097fb107cea3358b19bcbb4eb655fd67f8c, 72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
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.
References
- git.kernel.org/stable/c/bf75f14d755f9cfbb246e6cc011b53cdd5142de3 (opens in a new tab)
- git.kernel.org/stable/c/72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203 (opens in a new tab)
- git.kernel.org/stable/c/0a90e268cce7023f34087bfa4affb42e29ff5f45 (opens in a new tab)
- git.kernel.org/stable/c/5ec8f629a300cc40e746d6178f724bdff7683fa7 (opens in a new tab)
- git.kernel.org/stable/c/a3417097fb107cea3358b19bcbb4eb655fd67f8c (opens in a new tab)