CVE-2023-53621

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-10-07. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

memcontrol: ensure memcg acquired by id is properly set up

In the eviction recency check, we attempt to retrieve the memcg to which the folio belonged when it was evicted, by the memcg id stored in the shadow entry. However, there is a chance that the retrieved memcg is not the original memcg that has been killed, but a new one which happens to have the same id.

This is a somewhat unfortunate, but acceptable and rare inaccuracy in the heuristics. However, if we retrieve this new memcg between its allocation and when it is properly attached to the memcg hierarchy, we could run into the following NULL pointer exception during the memcg hierarchy traversal done in mem_cgroup_get_nr_swap_pages():

[ 155757.793456] BUG: kernel NULL pointer dereference, address: 00000000000000c0 [ 155757.807568] #PF: supervisor read access in kernel mode [ 155757.818024] #PF: error_code(0x0000) - not-present page [ 155757.828482] PGD 401f77067 P4D 401f77067 PUD 401f76067 PMD 0 [ 155757.839985] Oops: 0000 [#1] SMP [ 155757.887870] RIP: 0010:mem_cgroup_get_nr_swap_pages+0x3d/0xb0 [ 155757.899377] Code: 29 19 4a 02 48 39 f9 74 63 48 8b 97 c0 00 00 00 48 8b b7 58 02 00 00 48 2b b7 c0 01 00 00 48 39 f0 48 0f 4d c6 48 39 d1 74 42 <48> 8b b2 c0 00 00 00 48 8b ba 58 02 00 00 48 2b ba c0 01 00 00 48 [ 155757.937125] RSP: 0018:ffffc9002ecdfbc8 EFLAGS: 00010286 [ 155757.947755] RAX: 00000000003a3b1c RBX: 000007ffffffffff RCX: ffff888280183000 [ 155757.962202] RDX: 0000000000000000 RSI: 0007ffffffffffff RDI: ffff888bbc2d1000 [ 155757.976648] RBP: 0000000000000001 R08: 000000000000000b R09: ffff888ad9cedba0 [ 155757.991094] R10: ffffea0039c07900 R11: 0000000000000010 R12: ffff888b23a7b000 [ 155758.005540] R13: 0000000000000000 R14: ffff888bbc2d1000 R15: 000007ffffc71354 [ 155758.019991] FS: 00007f6234c68640(0000) GS:ffff88903f9c0000(0000) knlGS:0000000000000000 [ 155758.036356] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 155758.048023] CR2: 00000000000000c0 CR3: 0000000a83eb8004 CR4: 00000000007706e0 [ 155758.062473] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 155758.076924] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 155758.091376] PKRU: 55555554 [ 155758.096957] Call Trace: [ 155758.102016] [ 155758.106502] ? __die+0x78/0xc0 [ 155758.112793] ? page_fault_oops+0x286/0x380 [ 155758.121175] ? exc_page_fault+0x5d/0x110 [ 155758.129209] ? asm_exc_page_fault+0x22/0x30 [ 155758.137763] ? mem_cgroup_get_nr_swap_pages+0x3d/0xb0 [ 155758.148060] workingset_test_recent+0xda/0x1b0 [ 155758.157133] workingset_refault+0xca/0x1e0 [ 155758.165508] filemap_add_folio+0x4d/0x70 [ 155758.173538] page_cache_ra_unbounded+0xed/0x190 [ 155758.182919] page_cache_sync_ra+0xd6/0x1e0 [ 155758.191738] filemap_read+0x68d/0xdf0 [ 155758.199495] ? mlx5e_napi_poll+0x123/0x940 [ 155758.207981] ? __napi_schedule+0x55/0x90 [ 155758.216095] __x64_sys_pread64+0x1d6/0x2c0 [ 155758.224601] do_syscall_64+0x3d/0x80 [ 155758.232058] entry_SYSCALL_64_after_hwframe+0x46/0xb0 [ 155758.242473] RIP: 0033:0x7f62c29153b5 [ 155758.249938] Code: e8 48 89 75 f0 89 7d f8 48 89 4d e0 e8 b4 e6 f7 ff 41 89 c0 4c 8b 55 e0 48 8b 55 e8 48 8b 75 f0 8b 7d f8 b8 11 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 33 44 89 c7 48 89 45 f8 e8 e7 e6 f7 ff 48 8b [ 155758.288005] RSP: 002b:00007f6234c5ffd0 EFLAGS: 00000293 ORIG_RAX: 0000000000000011 [ 155758.303474] RAX: ffffffffffffffda RBX: 00007f628c4e70c0 RCX: 00007f62c29153b5 [ 155758.318075] RDX: 000000000003c041 RSI: 00007f61d2986000 RDI: 0000000000000076 [ 155758.332678] RBP: 00007f6234c5fff0 R08: 0000000000000000 R09: 0000000064d5230c [ 155758.347452] R10: 000000000027d450 R11: 0000000000000293 R12: 000000000003c041 [ 155758.362044] R13: 00007f61d2986000 R14: 00007f629e11b060 R15: 000000000027d450 [ 155758.376661]

This patch fixes the issue by moving the memcg's id publication from the alloc stage to ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

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

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). 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
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA 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: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

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.

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

October 7, 2025

Last Modified

February 5, 2026

Advisory Details (2)

Auto-updated Oct 8, 2026
Patch available.
Web page

memcontrol: ensure memcg acquired by id is properly set up - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b9d30c38ee859d833a51131b5b4b864c7a6219d0
Web page

memcontrol: ensure memcg acquired by id is properly set up - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6f0df8e16eb543167f2929cb756e695709a3551d

Vendor Advisories for CVE-2023-53621(2)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:4.18.0-553.27.1.el8_102024-11-05redhat
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
linuxKernel @ 6.5.4 (fixes >=6.3.0)—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.5.6-1: fixed in 6.5.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.5.6-1: fixed in 6.5.6-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 34× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 91 of 175 refreshes on record for this CVE.

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. 9 repeat rows among the latest 100 are merged into the row they repeat. The 84 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-10-20 21:14 UTCEG score recompute
  5. 2026-10-20 21:14 UTCVendor advisory
  6. 2026-10-20 21:14 UTCGHSA enrichmentGHSA-qhmw-vr57-jm8g · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-10-18 07:40 UTCEG score recompute
  11. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-10-12 18:12 UTCEG score recompute
  16. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-10-11 21:37 UTCEG score recompute
  18. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 9th percentile
Show 66 more
  1. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-10-02 04:10 UTCOSV refresh
  3. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-09-30 16:37 UTCEG score recompute
  5. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-09-12 22:36 UTCOSV refresh
  18. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  26. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  27. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  28. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  29. 2026-09-01 04:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  30. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  31. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  32. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  33. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  34. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  35. 2026-08-25 02:56 UTCOSV refresh
  36. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  37. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  38. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  39. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  40. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  41. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  42. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  43. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  44. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  45. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  46. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  47. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  48. 2026-08-08 19:55 UTCOSV refresh
  49. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  50. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  51. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  52. 2026-08-03 10:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  53. 2026-08-02 02:25 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  54. 2026-08-01 04:14 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  55. 2026-07-30 16:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  56. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  57. 2026-07-28 15:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  58. 2026-07-26 14:53 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  59. 2026-07-25 14:16 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  60. 2026-07-24 14:16 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  61. 2026-07-23 18:41 UTCOSV refresh
  62. 2026-07-23 14:16 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  63. 2026-07-23 02:29 UTCEG score recompute
  64. 2026-07-22 23:16 UTCEG score recompute
  65. 2026-07-22 14:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  66. 2026-07-21 15:23 UTCEPSS rescoreEPSS 0.2% · 8th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-53621?
CVE-2023-53621 is a high-severity vulnerability; its CVE record was published on October 7, 2025. In the Linux kernel, the following vulnerability has been resolved: memcontrol: ensure memcg acquired by id is properly set up In the eviction recency check, we attempt to retrieve the memcg to which the folio belonged when it was evicted, by the memcg id stored in the shadow entry. However, there…
When was the CVE record for CVE-2023-53621 published?
The CVE record for CVE-2023-53621 was published on October 7, 2025. 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 February 5, 2026; the record at its source may have been updated since.
Is CVE-2023-53621 actively exploited?
CVE-2023-53621 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53621?
CVE-2023-53621 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-53621?
A fix for CVE-2023-53621 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53621 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-2023-53621

Explore →

Is Your Infrastructure Affected by CVE-2023-53621?

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

Book a Demo →Browse All CVEs