CVE-2023-54019

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-24. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2025-205123 (ENISA EUVD) · GHSA-j7pj-g3hv-5hcw (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.1%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: use kernfs polling functions for PSI trigger polling

Destroying psi trigger in cgroup_file_release causes UAF issues when a cgroup is removed from under a polling process. This is happening because cgroup removal causes a call to cgroup_file_release while the actual file is still alive. Destroying the trigger at this point would also destroy its waitqueue head and if there is still a polling process on that file accessing the waitqueue, it will step on the freed pointer:

do_select vfs_poll do_rmdir cgroup_rmdir kernfs_drain_open_files cgroup_file_release cgroup_pressure_release psi_trigger_destroy wake_up_pollfree(&t->event_wait) // vfs_poll is unblocked synchronize_rcu kfree(t) poll_freewait -> UAF access to the trigger's waitqueue head

Patch [1] fixed this issue for epoll() case using wake_up_pollfree(), however the same issue exists for synchronous poll() case. The root cause of this issue is that the lifecycles of the psi trigger's waitqueue and of the file associated with the trigger are different. Fix this by using kernfs_generic_poll function when polling on cgroup-specific psi triggers. It internally uses kernfs_open_node->poll waitqueue head with its lifecycle tied to the file's lifecycle. This also renders the fix in [1] obsolete, so revert it.

[1] commit c2dbe32d5db5 ("sched/psi: Fix use-after-free in ep_remove_wait_queue()")

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.1% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.1%
EPSS %ILE
3rd
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.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). 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, and whom BOD 26-04 binds: 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 (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)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 Vulnrichment) · Technical impact total (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

December 24, 2025

Last Modified

October 15, 2026

Advisory Details (3)

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

sched/psi: use kernfs polling functions for PSI trigger polling - kernel/git/stable/linux.git - Linux kernel stable tree

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

sched/psi: use kernfs polling functions for PSI trigger polling - kernel/git/stable/linux.git - Linux kernel stable tree

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

sched/psi: use kernfs polling functions for PSI trigger polling - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/92cc0153324b6ae8577a39f5bf2cd83c9a34ea6a

Vendor Advisories for CVE-2023-54019(2)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-503.11.1.el9_52024-11-12redhat
linuxKernel @ 6.1.42 (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 ... 7.2~rc5-1~exp1 (498 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.38-4~bpo11+1 (8 versions)
  • every version up to 6.1.52-1: fixed in 6.1.52-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.11-1: fixed in 6.4.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.4.11-1: fixed in 6.4.11-1
—

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2023-54019?
CVE-2023-54019 is a high-severity vulnerability; its CVE record was published on December 24, 2025. In the Linux kernel, the following vulnerability has been resolved: sched/psi: use kernfs polling functions for PSI trigger polling Destroying psi trigger in cgroup_file_release causes UAF issues when a cgroup is removed from under a polling process. This is happening because cgroup removal causes…
When was the CVE record for CVE-2023-54019 published?
The CVE record for CVE-2023-54019 was published on December 24, 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2023-54019 actively exploited?
CVE-2023-54019 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-54019?
CVE-2023-54019 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2023-54019?
A fix for CVE-2023-54019 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-54019 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-54019

Explore →

Is Your Infrastructure Affected by CVE-2023-54019?

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