Answer in brief
CVE-2026-93240 records a Unknown severity vulnerability in memcg: make the v1 soft limit knob inert. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0a90e268cce7023f34087bfa4affb42e29ff5f45 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <5ec8f629a300cc40e746d6178f724bdff7683fa7 || >=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a3417097fb107cea3358b19bcbb4eb655fd67f8c || >=0 <6.12.110 || >=0 <6.18.51 || >=0 <7.2.5 | 72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203, 0a90e268cce7023f34087bfa4affb42e29ff5f45, 5ec8f629a300cc40e746d6178f724bdff7683fa7, a3417097fb107cea3358b19bcbb4eb655fd67f8c, 6.12.110, 6.18.51, 7.2.5 |
Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.