Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 27 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected e9d4e1ee788097484606c32122f146d802a9c5fb – < bf75f14d755f9cfbb246e6cc011b53cdd5142de3
    • affected e9d4e1ee788097484606c32122f146d802a9c5fb – < 72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203
    • affected e9d4e1ee788097484606c32122f146d802a9c5fb – < 0a90e268cce7023f34087bfa4affb42e29ff5f45
    • affected e9d4e1ee788097484606c32122f146d802a9c5fb – < 5ec8f629a300cc40e746d6178f724bdff7683fa7
    • affected e9d4e1ee788097484606c32122f146d802a9c5fb – < a3417097fb107cea3358b19bcbb4eb655fd67f8c
  • Linux · Linux

    • affected 6.3
    • unaffected < 6.3
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-93240 badge
[![CVE-2026-93240](https://cveledger.app/badge/CVE-2026-93240.svg)](https://cveledger.app/cve/CVE-2026-93240)

Record last updated .