CVE-2023-52707

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 2024-05-21. 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

Also known asEUVD-2023-57331 (ENISA EUVD) · GHSA-cw5r-8wj2-xpqf (GitHub Security Advisories)Source: ENISA EUVD

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.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

sched/psi: Fix use-after-free in ep_remove_wait_queue()

If a non-root cgroup gets removed when there is a thread that registered trigger and is polling on a pressure file within the cgroup, the polling waitqueue gets freed in the following path:

do_rmdir cgroup_rmdir kernfs_drain_open_files cgroup_file_release cgroup_pressure_release psi_trigger_destroy

However, the polling thread still has a reference to the pressure file and will access the freed waitqueue when the file is closed or upon exit:

fput ep_eventpoll_release ep_free ep_remove_wait_queue remove_wait_queue

This results in use-after-free as pasted below.

The fundamental problem here is that cgroup_file_release() (and consequently waitqueue's lifetime) is not tied to the file's real lifetime. Using wake_up_pollfree() here might be less than ideal, but it is in line with the comment at commit 42288cb44c4b ("wait: add wake_up_pollfree()") since the waitqueue's lifetime is not tied to file's one and can be considered as another special case. While this would be fixable by somehow making cgroup_file_release() be tied to the fput(), it would require sizable refactoring at cgroups or higher layer which might be more justifiable if we identify more cases like this.

BUG: KASAN: use-after-free in _raw_spin_lock_irqsave+0x60/0xc0 Write of size 4 at addr ffff88810e625328 by task a.out/4404

CPU: 19 PID: 4404 Comm: a.out Not tainted 6.2.0-rc6 #38 Hardware name: Amazon EC2 c5a.8xlarge/, BIOS 1.0 10/16/2017 Call Trace: dump_stack_lvl+0x73/0xa0 print_report+0x16c/0x4e0 kasan_report+0xc3/0xf0 kasan_check_range+0x2d2/0x310 _raw_spin_lock_irqsave+0x60/0xc0 remove_wait_queue+0x1a/0xa0 ep_free+0x12c/0x170 ep_eventpoll_release+0x26/0x30 __fput+0x202/0x400 task_work_run+0x11d/0x170 do_exit+0x495/0x1130 do_group_exit+0x100/0x100 get_signal+0xd67/0xde0 arch_do_signal_or_restart+0x2a/0x2b0 exit_to_user_mode_prepare+0x94/0x100 syscall_exit_to_user_mode+0x20/0x40 do_syscall_64+0x52/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd

Allocated by task 4404:

kasan_set_track+0x3d/0x60 __kasan_kmalloc+0x85/0x90 psi_trigger_create+0x113/0x3e0 pressure_write+0x146/0x2e0 cgroup_file_write+0x11c/0x250 kernfs_fop_write_iter+0x186/0x220 vfs_write+0x3d8/0x5c0 ksys_write+0x90/0x110 do_syscall_64+0x43/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd

Freed by task 4407:

kasan_set_track+0x3d/0x60 kasan_save_free_info+0x27/0x40 ____kasan_slab_free+0x11d/0x170 slab_free_freelist_hook+0x87/0x150 __kmem_cache_free+0xcb/0x180 psi_trigger_destroy+0x2e8/0x310 cgroup_file_release+0x4f/0xb0 kernfs_drain_open_files+0x165/0x1f0 kernfs_drain+0x162/0x1a0 __kernfs_remove+0x1fb/0x310 kernfs_remove_by_name_ns+0x95/0xe0 cgroup_addrm_files+0x67f/0x700 cgroup_destroy_locked+0x283/0x3c0 cgroup_rmdir+0x29/0x100 kernfs_iop_rmdir+0xd1/0x140 vfs_rmdir+0xfe/0x240 do_rmdir+0x13d/0x280 __x64_sys_rmdir+0x2c/0x30 do_syscall_64+0x43/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd

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.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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.3%
EPSS %ILE
18th
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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 every mission impact level.CISA BOD 26-04: 60 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 SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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)60 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 Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

May 21, 2024

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Aug 4, 2026
Patch available.
Web page

sched/psi: Fix use-after-free in ep_remove_wait_queue() - kernel/git/stable/linux.git - Linux kernel stable tree

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

sched/psi: Fix use-after-free in ep_remove_wait_queue() - kernel/git/stable/linux.git - Linux kernel stable tree

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

sched/psi: Fix use-after-free in ep_remove_wait_queue() - kernel/git/stable/linux.git - Linux kernel stable tree

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

sched/psi: Fix use-after-free in ep_remove_wait_queue() - kernel/git/stable/linux.git - Linux kernel stable tree

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

sched/psi: Fix use-after-free in ep_remove_wait_queue() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7caeb5457bd01ccba0df1d6f4872f20d28e50b38

Vendor Advisories for CVE-2023-52707(5)

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

Patch Availability(6)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-rt-0:4.18.0-553.16.1.rt7.357.el8_102024-08-08redhat
redhatkernel-0:4.18.0-553.16.1.el8_102024-08-08redhat
redhatkernel-0:5.14.0-284.75.1.el9_22024-07-24redhat
redhatkernel-rt-0:5.14.0-284.75.1.rt14.360.el9_22024-07-24redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 5.4.232 (fixes >=5.2.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (25 versions)
  • every version up to 5.10.178-1: fixed in 5.10.178-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.15-1: fixed in 6.1.15-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.15-1: fixed in 6.1.15-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.15-1: fixed in 6.1.15-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 41× 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 93 of 215 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. 7 repeat rows among the latest 100 are merged into the row they repeat. The 122 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)· as of October 31, 2026

Frequently asked(5)

What is CVE-2023-52707?
CVE-2023-52707 is a high-severity vulnerability; its CVE record was published on May 21, 2024. In the Linux kernel, the following vulnerability has been resolved: sched/psi: Fix use-after-free in ep_remove_wait_queue() If a non-root cgroup gets removed when there is a thread that registered trigger and is polling on a pressure file within the cgroup, the polling waitqueue gets freed in the…
When was the CVE record for CVE-2023-52707 published?
The CVE record for CVE-2023-52707 was published on May 21, 2024. 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2023-52707 actively exploited?
CVE-2023-52707 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-52707?
CVE-2023-52707 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-52707?
A fix for CVE-2023-52707 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-52707 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-52707

Explore →

Is Your Infrastructure Affected by CVE-2023-52707?

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

Book a Demo →Browse All CVEs