{"api_version":"1","generated_at":"2026-10-07T22:04:03+00:00","cve":"CVE-2026-93240","urls":{"html":"https://cve.report/CVE-2026-93240","api":"https://cve.report/api/cve/CVE-2026-93240.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-93240","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-93240"},"summary":{"title":"memcg: make the v1 soft limit knob inert","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemcg: make the v1 soft limit knob inert\n\nThe v1 soft limit has been deprecated since v6.12 and nobody has reported\ndepending on it.  Start the removal by decoupling the interface from the\nimplementation: keep memory.soft_limit_in_bytes, but ignore writes to it\nand always report the maximum value on read similar to what\nmemory.kmem.limit_in_bytes already does.\n\nWrites are still parsed, so malformed input keeps returning -EINVAL.  The\nknob now also behaves the same everywhere: it used to return -EOPNOTSUPP\non PREEMPT_RT, where soft limit reclaim has always been disabled.\n\nThis also fixes the syzbot report linked below.  Soft limit reclaim is the\nonly caller that runs shrink_lruvec() from kswapd against a specific\nmemcg, so it is the only way to reach lru_gen_shrink_lruvec() and in turn\nset_mm_walk(), which warns when called from kswapd.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-24 16:17:19","updated_at":"2026-09-25 13:17:18"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/a3417097fb107cea3358b19bcbb4eb655fd67f8c","name":"https://git.kernel.org/stable/c/a3417097fb107cea3358b19bcbb4eb655fd67f8c","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0a90e268cce7023f34087bfa4affb42e29ff5f45","name":"https://git.kernel.org/stable/c/0a90e268cce7023f34087bfa4affb42e29ff5f45","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203","name":"https://git.kernel.org/stable/c/72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5ec8f629a300cc40e746d6178f724bdff7683fa7","name":"https://git.kernel.org/stable/c/5ec8f629a300cc40e746d6178f724bdff7683fa7","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-93240","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93240","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e9d4e1ee788097484606c32122f146d802a9c5fb 72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e9d4e1ee788097484606c32122f146d802a9c5fb 0a90e268cce7023f34087bfa4affb42e29ff5f45 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e9d4e1ee788097484606c32122f146d802a9c5fb 5ec8f629a300cc40e746d6178f724bdff7683fa7 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e9d4e1ee788097484606c32122f146d802a9c5fb a3417097fb107cea3358b19bcbb4eb655fd67f8c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.3","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.3 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.110 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.51 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.5 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"93240","cve":"CVE-2026-93240","epss":"0.002180000","percentile":"0.110230000","score_date":"2026-09-27","updated_at":"2026-09-28 00:02:24"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["Documentation/admin-guide/cgroup-v1/memory.rst","mm/memcontrol-v1.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203","status":"affected","version":"e9d4e1ee788097484606c32122f146d802a9c5fb","versionType":"git"},{"lessThan":"0a90e268cce7023f34087bfa4affb42e29ff5f45","status":"affected","version":"e9d4e1ee788097484606c32122f146d802a9c5fb","versionType":"git"},{"lessThan":"5ec8f629a300cc40e746d6178f724bdff7683fa7","status":"affected","version":"e9d4e1ee788097484606c32122f146d802a9c5fb","versionType":"git"},{"lessThan":"a3417097fb107cea3358b19bcbb4eb655fd67f8c","status":"affected","version":"e9d4e1ee788097484606c32122f146d802a9c5fb","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["Documentation/admin-guide/cgroup-v1/memory.rst","mm/memcontrol-v1.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.3"},{"lessThan":"6.3","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.110","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.51","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.110","versionStartIncluding":"6.3","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.51","versionStartIncluding":"6.3","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.5","versionStartIncluding":"6.3","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc2","versionStartIncluding":"6.3","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemcg: make the v1 soft limit knob inert\n\nThe v1 soft limit has been deprecated since v6.12 and nobody has reported\ndepending on it.  Start the removal by decoupling the interface from the\nimplementation: keep memory.soft_limit_in_bytes, but ignore writes to it\nand always report the maximum value on read similar to what\nmemory.kmem.limit_in_bytes already does.\n\nWrites are still parsed, so malformed input keeps returning -EINVAL.  The\nknob now also behaves the same everywhere: it used to return -EOPNOTSUPP\non PREEMPT_RT, where soft limit reclaim has always been disabled.\n\nThis also fixes the syzbot report linked below.  Soft limit reclaim is the\nonly caller that runs shrink_lruvec() from kswapd against a specific\nmemcg, so it is the only way to reach lru_gen_shrink_lruvec() and in turn\nset_mm_walk(), which warns when called from kswapd."}],"providerMetadata":{"dateUpdated":"2026-09-25T12:42:40.764Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/72fb67f6e0e5d78e4f34cf9929d1afdb0fd54203"},{"url":"https://git.kernel.org/stable/c/0a90e268cce7023f34087bfa4affb42e29ff5f45"},{"url":"https://git.kernel.org/stable/c/5ec8f629a300cc40e746d6178f724bdff7683fa7"},{"url":"https://git.kernel.org/stable/c/a3417097fb107cea3358b19bcbb4eb655fd67f8c"}],"title":"memcg: make the v1 soft limit knob inert","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-93240","datePublished":"2026-09-24T15:34:32.134Z","dateReserved":"2026-09-17T16:02:15.095Z","dateUpdated":"2026-09-25T12:42:40.764Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-24 16:17:19","lastModifiedDate":"2026-09-25 13:17:18","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"93240","Ordinal":"1","Title":"memcg: make the v1 soft limit knob inert","CVE":"CVE-2026-93240","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"93240","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nmemcg: make the v1 soft limit knob inert\n\nThe v1 soft limit has been deprecated since v6.12 and nobody has reported\ndepending on it.  Start the removal by decoupling the interface from the\nimplementation: keep memory.soft_limit_in_bytes, but ignore writes to it\nand always report the maximum value on read similar to what\nmemory.kmem.limit_in_bytes already does.\n\nWrites are still parsed, so malformed input keeps returning -EINVAL.  The\nknob now also behaves the same everywhere: it used to return -EOPNOTSUPP\non PREEMPT_RT, where soft limit reclaim has always been disabled.\n\nThis also fixes the syzbot report linked below.  Soft limit reclaim is the\nonly caller that runs shrink_lruvec() from kswapd against a specific\nmemcg, so it is the only way to reach lru_gen_shrink_lruvec() and in turn\nset_mm_walk(), which warns when called from kswapd.","Type":"Description","Title":"memcg: make the v1 soft limit knob inert"}]}}}