CVE-2023-52973

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

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.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

March 27, 2025

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

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
generic

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
generic

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
generic

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
generic

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
generic

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
generic

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 / EcosystemFixed in / 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—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.

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 107 total refreshes for this CVE.

  1. 2026-08-05 19:15 UTCEPSS rescore
  2. 2026-08-05 19:15 UTCEPSS rescore
  3. 2026-08-05 10:21 UTCEG score recompute
  4. 2026-08-05 10:21 UTCVendor advisory
  5. 2026-08-05 10:21 UTCGHSA enrichment
  6. 2026-08-04 10:36 UTCEPSS rescore
  7. 2026-08-04 09:45 UTCEG score recompute
  8. 2026-08-04 09:45 UTCVendor advisory
  9. 2026-08-04 09:45 UTCGHSA enrichment
  10. 2026-08-03 10:34 UTCEPSS rescore
  11. 2026-08-02 02:25 UTCEPSS rescore
  12. 2026-08-02 02:25 UTCEPSS rescore
  13. 2026-08-01 04:14 UTCEPSS rescore
  14. 2026-07-30 16:26 UTCEPSS rescore
  15. 2026-07-30 01:29 UTCEPSS rescore
  16. 2026-07-28 15:34 UTCEPSS rescore
  17. 2026-07-28 15:34 UTCEPSS rescore
  18. 2026-07-26 14:53 UTCEPSS rescore
  19. 2026-07-25 14:16 UTCEPSS rescore
  20. 2026-07-24 14:16 UTCEPSS rescore
  21. 2026-07-24 11:11 UTCOSV refresh
  22. 2026-07-23 14:16 UTCEPSS rescore
  23. 2026-07-23 02:29 UTCEG score recompute
  24. 2026-07-22 23:16 UTCEG score recompute
  25. 2026-07-22 14:07 UTCEPSS rescore
Show 75 more
  1. 2026-07-22 14:07 UTCEPSS rescore
  2. 2026-07-21 15:23 UTCEPSS rescore
  3. 2026-07-20 17:06 UTCEPSS rescore
  4. 2026-07-19 14:30 UTCEPSS rescore
  5. 2026-07-19 14:29 UTCEPSS rescore
  6. 2026-07-19 02:27 UTCEPSS rescore
  7. 2026-07-19 02:27 UTCEPSS rescore
  8. 2026-07-18 10:03 UTCEPSS rescore
  9. 2026-07-18 10:03 UTCEPSS rescore
  10. 2026-07-16 17:01 UTCEPSS rescore
  11. 2026-07-15 16:56 UTCEPSS rescore
  12. 2026-07-15 01:59 UTCEPSS rescore
  13. 2026-07-15 01:59 UTCEPSS rescore
  14. 2026-07-13 22:28 UTCEPSS rescore
  15. 2026-07-13 22:28 UTCEPSS rescore
  16. 2026-07-13 06:11 UTCEPSS rescore
  17. 2026-07-12 05:45 UTCEPSS rescore
  18. 2026-07-12 05:45 UTCEPSS rescore
  19. 2026-07-11 08:26 UTCEPSS rescore
  20. 2026-07-09 19:08 UTCEPSS rescore
  21. 2026-07-07 13:45 UTCEPSS rescore
  22. 2026-07-07 13:44 UTCEPSS rescore
  23. 2026-07-07 06:21 UTCOSV refresh
  24. 2026-07-06 16:26 UTCEPSS rescore
  25. 2026-07-06 16:26 UTCEPSS rescore
  26. 2026-07-06 02:22 UTCEPSS rescore
  27. 2026-07-06 02:22 UTCEPSS rescore
  28. 2026-07-05 02:29 UTCEPSS rescore
  29. 2026-07-04 06:29 UTCEPSS rescore
  30. 2026-07-01 15:05 UTCEPSS rescore
  31. 2026-06-30 23:21 UTCEPSS rescore
  32. 2026-06-30 23:21 UTCEPSS rescore
  33. 2026-06-29 14:05 UTCEPSS rescore
  34. 2026-06-28 14:06 UTCEPSS rescore
  35. 2026-06-28 14:06 UTCEPSS rescore
  36. 2026-06-28 04:55 UTCEPSS rescore
  37. 2026-06-27 03:07 UTCEPSS rescore
  38. 2026-06-25 13:48 UTCEPSS rescore
  39. 2026-06-25 13:48 UTCEPSS rescore
  40. 2026-06-24 14:04 UTCEPSS rescore
  41. 2026-06-24 14:04 UTCEPSS rescore
  42. 2026-06-23 21:31 UTCEPSS rescore
  43. 2026-06-23 21:31 UTCEPSS rescore
  44. 2026-06-22 14:24 UTCEPSS rescore
  45. 2026-06-22 14:24 UTCEPSS rescore
  46. 2026-06-21 14:55 UTCEPSS rescore
  47. 2026-06-21 14:55 UTCEPSS rescore
  48. 2026-06-21 01:58 UTCEPSS rescore
  49. 2026-06-21 01:58 UTCEPSS rescore
  50. 2026-06-19 19:24 UTCEPSS rescore
  51. 2026-06-19 19:24 UTCEPSS rescore
  52. 2026-06-18 17:51 UTCEPSS rescore
  53. 2026-06-18 17:35 UTCOSV refresh
  54. 2026-06-17 17:51 UTCEPSS rescore
  55. 2026-06-16 17:51 UTCEPSS rescore
  56. 2026-06-16 17:51 UTCEPSS rescore
  57. 2026-06-15 17:47 UTCEPSS rescore
  58. 2026-06-14 23:16 UTCEPSS rescore
  59. 2026-06-13 22:59 UTCEPSS rescore
  60. 2026-06-13 22:59 UTCEPSS rescore
  61. 2026-06-12 23:11 UTCEPSS rescore
  62. 2026-06-11 13:59 UTCEPSS rescore
  63. 2026-06-10 22:17 UTCEPSS rescore
  64. 2026-06-08 14:16 UTCEPSS rescore
  65. 2026-06-08 14:16 UTCEPSS rescore
  66. 2026-06-07 15:24 UTCEPSS rescore
  67. 2026-06-07 15:24 UTCEPSS rescore
  68. 2026-06-06 13:46 UTCEPSS rescore
  69. 2026-06-06 13:46 UTCEPSS rescore
  70. 2026-06-05 22:46 UTCEPSS rescore
  71. 2026-06-05 22:46 UTCEPSS rescore
  72. 2026-06-04 13:11 UTCEPSS rescore
  73. 2026-06-04 13:11 UTCEPSS rescore
  74. 2026-06-02 20:12 UTCEPSS rescore
  75. 2026-06-02 20:12 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-52973?
CVE-2023-52973 is a high vulnerability published on March 27, 2025. In the Linux kernel, the following vulnerability has been resolved: vcscreen: move load of struct vcdata pointer in vcs_read() to avoid UAF After a call to consoleunlock() in vcsread() the vc_data struct can be freed by vcdeallocate(). Because of that, the struct vcdata pointer load must be done at…
When was CVE-2023-52973 disclosed?
CVE-2023-52973 was first published in the National Vulnerability Database on March 27, 2025, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-52973 actively exploited?
CVE-2023-52973 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.9% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-52973, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs