CVE-2023-52973

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-03-27. 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-59747 (ENISA EUVD) · GHSA-34qc-h2vp-hq88 (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:

vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF

After a call to console_unlock() in vcs_read() the vc_data struct can be freed by vc_deallocate(). Because of that, the struct vc_data pointer load must be done at the top of while loop in vcs_read() to avoid a UAF when vcs_size() is called.

Syzkaller reported a UAF in vcs_size().

BUG: KASAN: use-after-free in vcs_size (drivers/tty/vt/vc_screen.c:215) Read of size 4 at addr ffff8881137479a8 by task 4a005ed81e27e65/1537

CPU: 0 PID: 1537 Comm: 4a005ed81e27e65 Not tainted 6.2.0-rc5 #1 Hardware name: Red Hat KVM, BIOS 1.15.0-2.module Call Trace: __asan_report_load4_noabort (mm/kasan/report_generic.c:350) vcs_size (drivers/tty/vt/vc_screen.c:215) vcs_read (drivers/tty/vt/vc_screen.c:415) vfs_read (fs/read_write.c:468 fs/read_write.c:450) ...

Allocated by task 1191: ... kmalloc_trace (mm/slab_common.c:1069) vc_allocate (./include/linux/slab.h:580 ./include/linux/slab.h:720 drivers/tty/vt/vt.c:1128 drivers/tty/vt/vt.c:1108) con_install (drivers/tty/vt/vt.c:3383) tty_init_dev (drivers/tty/tty_io.c:1301 drivers/tty/tty_io.c:1413 drivers/tty/tty_io.c:1390) tty_open (drivers/tty/tty_io.c:2080 drivers/tty/tty_io.c:2126) chrdev_open (fs/char_dev.c:415) do_dentry_open (fs/open.c:883) vfs_open (fs/open.c:1014) ...

Freed by task 1548: ... kfree (mm/slab_common.c:1021) vc_port_destruct (drivers/tty/vt/vt.c:1094) tty_port_destructor (drivers/tty/tty_port.c:296) tty_port_put (drivers/tty/tty_port.c:312) vt_disallocate_all (drivers/tty/vt/vt_ioctl.c:662 (discriminator 2)) vt_ioctl (drivers/tty/vt/vt_ioctl.c:903) tty_ioctl (drivers/tty/tty_io.c:2776) ...

The buggy address belongs to the object at ffff888113747800 which belongs to the cache kmalloc-1k of size 1024 The buggy address is located 424 bytes inside of 1024-byte region [ffff888113747800, ffff888113747c00)

The buggy address belongs to the physical page: page:00000000b3fe6c7c refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x113740 head:00000000b3fe6c7c order:3 compound_mapcount:0 subpages_mapcount:0 compound_pincount:0 anon flags: 0x17ffffc0010200(slab|head|node=0|zone=2|lastcpupid=0x1fffff) raw: 0017ffffc0010200 ffff888100042dc0 0000000000000000 dead000000000001 raw: 0000000000000000 0000000000100010 00000001ffffffff 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff888113747880: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff888113747900: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb > ffff888113747980: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff888113747a00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff888113747a80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ================================================================== Disabling lock debugging due to kernel taint

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 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.3%
EPSS %ILE
21st
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 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

March 27, 2025

Last Modified

August 5, 2026

Advisory Details (7)

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

vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/226fae124b2dac217ea5436060d623ff3385bc34
Web page

vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8506f16aae9daf354e3732bcfd447e2a97f023df
Web page

vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF - kernel/git/stable/linux.git - Linux kernel stable tree

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

vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/55515d7d8743b71b80bfe68e89eb9d92630626ab
Web page

vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF - kernel/git/stable/linux.git - Linux kernel stable tree

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

vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6332f52f44b9776568bf3c0b714ddfb0bb175e78
Web page

vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/af79ea9a2443016f64d8fd8d72020cc874f0e066

Vendor Advisories for CVE-2023-52973(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-0:4.18.0-553.el8_102024-05-22redhat
redhatkernel-0:5.14.0-427.13.1.el9_42024-04-30redhat
redhatkernel-0:4.18.0-477.43.1.el8_82024-01-30redhat
redhatkernel-0:5.14.0-284.48.1.el9_22024-01-25redhat
redhatkernel-rt-0:5.14.0-284.48.1.rt14.333.el9_22024-01-25redhat
linuxKernel @ 4.14.329 (fixes >=2.6.38)—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.11-1: fixed in 6.1.11-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.11-1: fixed in 6.1.11-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.11-1: fixed in 6.1.11-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 94 of 200 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 106 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.3% · 21st percentile
  2. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  3. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  4. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  5. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  6. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  7. 2026-10-27 20:09 UTCEG score recompute
  8. 2026-10-27 20:09 UTCVendor advisory
  9. 2026-10-27 20:09 UTCGHSA enrichmentGHSA-34qc-h2vp-hq88 · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  11. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  12. 2026-10-25 17:28 UTCEG score recompute
  13. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  14. 2026-10-24 16:29 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  15. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  16. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  17. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  18. 2026-10-20 21:16 UTCEG score recompute
  19. 2026-10-20 21:16 UTCVendor advisory
  20. 2026-10-20 21:16 UTCGHSA enrichmentGHSA-34qc-h2vp-hq88 · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  22. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-10-19 15:25 UTCOSV refresh
  24. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  25. 2026-10-18 07:41 UTCEG score recompute
Show 69 more
  1. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  3. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  4. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  5. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-10-12 18:13 UTCEG score recompute
  7. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  8. 2026-10-11 21:38 UTCEG score recompute
  9. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  12. 2026-10-08 17:06 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  13. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  14. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  17. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  19. 2026-09-30 16:37 UTCEG score recompute
  20. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  21. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  22. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-09-26 21:12 UTCOSV refresh
  24. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  26. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  27. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  28. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  29. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  30. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  31. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  32. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  33. 2026-09-12 14:58 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  34. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  35. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.3% · 21st percentile
  36. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  37. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  38. 2026-09-07 06:48 UTCOSV refresh
  39. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  40. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  41. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  42. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  43. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  44. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  45. 2026-09-01 04:36 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  46. 2026-08-30 19:15 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  47. 2026-08-30 01:20 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  48. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  49. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  50. 2026-08-26 14:44 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  51. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  52. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  53. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  54. 2026-08-20 22:53 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  55. 2026-08-20 16:31 UTCOSV refresh
  56. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  57. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  58. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  59. 2026-08-16 02:12 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  60. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  61. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  62. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  63. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  64. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  65. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  66. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  67. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  68. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  69. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.3% · 20th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-52973?
CVE-2023-52973 is a high-severity vulnerability; its CVE record was published on March 27, 2025. In the Linux kernel, the following vulnerability has been resolved: vc_screen: move load of struct vc_data pointer in vcs_read() to avoid UAF After a call to console_unlock() in vcs_read() the vc_data struct can be freed by vc_deallocate(). Because of that, the struct vc_data pointer load must be…
When was the CVE record for CVE-2023-52973 published?
The CVE record for CVE-2023-52973 was published on March 27, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2023-52973 actively exploited?
CVE-2023-52973 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-52973?
CVE-2023-52973 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-52973?
A fix for CVE-2023-52973 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-52973 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-52973

Explore →

Is Your Infrastructure Affected by CVE-2023-52973?

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

Book a Demo →Browse All CVEs