CVE-2026-93240
CVE CVE-2026-93240EUVD EUVD-2026-86246Published 2026-09-24T15:34:32.000ZLast changed 2026-09-25T12:42:40.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.12.110; e9d4e1ee788097484606c32122f146d802a9c5fb <0a90e268cce7023f34087bfa4affb42e29ff5f45; e9d4e1ee788097484606c32122f146d802a9c5fb <5ec8f629a300cc40e746d6178f724bdff7683fa7; 6.3; e9d4e1ee788097484606c32122f146d802a9c5fb <a3417097fb107cea3358b19bcbb4eb655fd67f8c; patch: 0; patch: 6.18.51; e9d4e1ee788097484606c32122f146d802a9c5fb <72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203; patch: 7.2.5; patch: 7.3-rc2
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.