Skip to main content
VulnerabilityPublished Updated

CVE-2026-93240: Linux kernel · memcg: make the v1 soft limit knob inert

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in bf75f14d755f9cfbb246e6cc011b53cdd5142de3 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 14:18 UTC

Severity
Unrated

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

  1. Disclosed: evidence found.

    CVE published 24 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e9d4e1ee788097484606c32122f146d802a9c5fb, < bf75f14d755f9cfbb246e6cc011b53cdd5142de3
Fixed in
  • bf75f14d755f9cfbb246e6cc011b53cdd5142de3
LinuxLinuxAffected
  • ≥ e9d4e1ee788097484606c32122f146d802a9c5fb, < a3417097fb107cea3358b19bcbb4eb655fd67f8c
Fixed in
  • a3417097fb107cea3358b19bcbb4eb655fd67f8c
LinuxLinuxAffected
  • ≥ e9d4e1ee788097484606c32122f146d802a9c5fb, < 72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203
Fixed in
  • 72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203
LinuxLinuxAffected
  • ≥ e9d4e1ee788097484606c32122f146d802a9c5fb, < 5ec8f629a300cc40e746d6178f724bdff7683fa7
Fixed in
  • 5ec8f629a300cc40e746d6178f724bdff7683fa7
LinuxLinuxAffected
  • ≥ e9d4e1ee788097484606c32122f146d802a9c5fb, < 0a90e268cce7023f34087bfa4affb42e29ff5f45
Fixed in
  • 0a90e268cce7023f34087bfa4affb42e29ff5f45
LinuxLinuxAffected
  • =6.3
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

Community reviews

Loading reviews…