CVE-2026-93241

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-86247 (ENISA EUVD) · GHSA-vxm3-j3p3-g54x (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

memcg: bypass the reclaim and oom killer for dying tasks once oom_reaper is done

At Meta, we are seeing instances where an OOM killed job is stuck in the exit path for several hours. In one particular case, the job was stuck for more than 8 hours and I had to manually remove the memory.max limits to allow the process to exit.

The job was a single process job and had ~55 GiB memory.max and zswap enabled. It had almost 0 anon in memory and ~111 GiB in zswap compressed to ~51 GiB zswap pool (i.e. almost all of memory.current was zswap). Nothing was left on the LRUs to reclaim.

On further inspection, I observed ~20k threads of that process stuck with the following stack:

[<0>] mem_cgroup_out_of_memory+0x4e/0xa0 [<0>] charge_memcg+0x8bf/0x990 [<0>] mem_cgroup_swapin_charge_folio+0x4e/0x80 [<0>] __read_swap_cache_async+0x10c/0x260 [<0>] swapin_readahead+0x116/0x3f0 [<0>] do_swap_page+0x13c/0x1ce0 [<0>] handle_mm_fault+0x61d/0x11f0 [<0>] do_user_addr_fault+0x3e7/0x6d0 [<0>] exc_page_fault+0x8f/0x110 [<0>] asm_exc_page_fault+0x22/0x30 [<0>] __get_user_8+0x14/0x20 [<0>] futex_cleanup+0x27/0x1c0 [<0>] futex_exit_release+0x47/0x60 [<0>] do_exit+0x107/0x940 [<0>] do_group_exit+0x81/0xa0 [<0>] get_signal+0x2b1/0x6e0 [<0>] arch_do_signal_or_restart+0x1a/0x1c0 [<0>] exit_to_user_mode_loop+0xa8/0x1c0 [<0>] do_syscall_64+0x152/0x250 [<0>] entry_SYSCALL_64_after_hwframe+0x4b/0x53

In addition the dmesg was filled with "Out of memory and no killable processes..." messages.

I have no idea why oom reaper was not able to reap/unmap the process. My guess is that since oom reaper tries to acquire mmap_lock in read mode limited number of times and then gives up, there might be a thread of that process which had mmap_lock in write mode at that time.

My initial suspicion was the futex_cleanup and kernel page fault causing infinite fault and charge retries but that was put to rest in previous discussions happened on similar problem [1].

My current theory is that it is just a simple slow serialization behind the oom_lock. Unlike page allocator, memcg charge code takes the oom_lock without the "try". Though memcg oom code uses mutex_lock_killable(), note that in the call stack get_signal() consumes SIGKILL (or sigdelset(SIGKILL)) before calling do_group_exit(). So this mutex_lock_killable() is just a mutex_lock() here. Therefore 10s of thousands of threads are waiting on oom_lock and one by one they get -EFAULT from get_user() in the futex cleanup code and bails out.

Discussion from [1] led to commit a75ffa26122b ("memcg, oom: do not bypass oom killer for dying tasks") which routes dying tasks into the OOM path precisely so the oom_reaper can reap their mm and free the memory asynchronously. But the reaper is best-effort and one-shot: if it cannot take mmap_lock for read (e.g. a sibling thread holds it for write) it sets MMF_OOM_SKIP and never retries, leaving only the glacial oom_lock-serialized synchronous drain.

Once MMF_OOM_SKIP is set there is no more asynchronous reclaim coming for the mm, so a dying task charging against it has nothing left to wait for: it frees its memory only once it finishes exiting. Running reclaim and the (no-victim) OOM killer for it is then pointless, and doing it for 10s of thousands of exiting threads is what serializes them behind oom_lock. So before reclaim, if current is an OOM victim whose reaper is done, fail the charge.

Reproduced with 20k threads, each parking a robust futex head on its own zswapped page, OOM-group-killed while a sibling holds mmap_lock for write so the reaper gives up and sets MMF_OOM_SKIP. Tested on next-20260728 and baseline show ~90 seconds exit time while with the patch the exit time reduced to ~3 seconds.

CVSS
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 24, 2026

Last Modified

October 19, 2026

Vendor Advisories for CVE-2026-93241(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.18.51 (fixes >=6.16.0)—osv

These rows come from OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (180 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 7× in last 7d / 30× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 83 is merged into the row it repeats.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  3. 2026-11-19 18:38 UTCEchelonGraph re-scored
  4. 2026-11-19 18:38 UTCGHSA enrichmentGHSA-vxm3-j3p3-g54x
  5. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  6. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  7. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  8. 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  9. 2026-11-15 17:04 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  10. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  11. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  13. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  14. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  15. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  16. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  17. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  18. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  19. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  20. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  21. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  22. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  23. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  24. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  25. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
Show 57 more
  1. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  2. 2026-10-28 09:55 UTCOSV refresh
  3. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  4. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  5. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  6. 2026-10-25 13:50 UTCEchelonGraph re-scored
  7. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  8. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  10. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  11. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  12. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  13. 2026-10-19 10:44 UTCGHSA enrichmentGHSA-vxm3-j3p3-g54x
  14. 2026-10-19 10:25 UTCNVD update
  15. 2026-10-19 09:57 UTCEchelonGraph re-scored
  16. 2026-10-19 09:57 UTCGHSA enrichmentGHSA-vxm3-j3p3-g54x
  17. 2026-10-19 09:39 UTCMITRE cvelistV5
  18. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  19. 2026-10-18 02:59 UTCEchelonGraph re-scored
  20. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  21. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  22. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  23. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  24. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  25. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  26. 2026-10-12 14:43 UTCEchelonGraph re-scored
  27. 2026-10-11 21:24 UTCGHSA enrichmentGHSA-vxm3-j3p3-g54x
  28. 2026-10-11 19:12 UTCEchelonGraph re-scored
  29. 2026-10-11 16:28 UTCEchelonGraph re-scored
  30. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  31. 2026-10-11 13:42 UTCEchelonGraph re-scored
  32. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  33. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  34. 2026-10-09 04:06 UTCGHSA enrichmentGHSA-vxm3-j3p3-g54x
  35. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  36. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  37. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  38. 2026-10-06 10:48 UTCGHSA enrichmentGHSA-vxm3-j3p3-g54x
  39. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  40. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  41. 2026-10-03 17:31 UTCGHSA enrichmentGHSA-vxm3-j3p3-g54x
  42. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  43. 2026-10-01 00:16 UTCEchelonGraph re-scored
  44. 2026-10-01 00:16 UTCGHSA enrichmentGHSA-vxm3-j3p3-g54x
  45. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  46. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  47. 2026-09-28 06:38 UTCEchelonGraph re-scored
  48. 2026-09-28 06:38 UTCGHSA enrichmentGHSA-vxm3-j3p3-g54x
  49. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  50. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  51. 2026-09-25 13:24 UTCGHSA enrichmentGHSA-vxm3-j3p3-g54x
  52. 2026-09-25 13:18 UTCNVD update
  53. 2026-09-25 12:57 UTCGHSA enrichmentGHSA-vxm3-j3p3-g54x
  54. 2026-09-25 12:54 UTCMITRE cvelistV5
  55. 2026-09-24 16:30 UTCNVD update
  56. 2026-09-24 15:47 UTCEchelonGraph re-scored
  57. 2026-09-24 15:46 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-93241?
CVE-2026-93241 is a vulnerability whose severity is not yet rated; its CVE record was published on September 24, 2026. In the Linux kernel, the following vulnerability has been resolved: memcg: bypass the reclaim and oom killer for dying tasks once oom_reaper is done At Meta, we are seeing instances where an OOM killed job is stuck in the exit path for several hours. In one particular case, the job was stuck for…
When was the CVE record for CVE-2026-93241 published?
The CVE record for CVE-2026-93241 was published on September 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-93241 actively exploited?
CVE-2026-93241 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-93241?
A fix for CVE-2026-93241 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-93241 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-93241

Explore →

Is Your Infrastructure Affected by CVE-2026-93241?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.