---
id: CVE-2026-93240
title: |-
  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
summary: |-
  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 th…
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    0a90e268cce7023f34087bfa4affb42e29ff5f45
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    5ec8f629a300cc40e746d6178f724bdff7683fa7
  - >-
    Linux >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <
    a3417097fb107cea3358b19bcbb4eb655fd67f8c
  - Linux < 6.12.110
  - Linux < 6.18.51
  - Linux < 7.2.5
  - Linux (all versions)
published: '2026-09-24'
updated: '2026-09-25'
sourceUpdated: '2026-09-25T13:17:18.003'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-93240'
references:
  - url: 'https://git.kernel.org/stable/c/0a90e268cce7023f34087bfa4affb42e29ff5f45'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/5ec8f629a300cc40e746d6178f724bdff7683fa7'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a3417097fb107cea3358b19bcbb4eb655fd67f8c'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
ingestedAt: '2026-09-24T15:45:56.657Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.