CVE-2023-53090

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2025-05-02. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.1EG
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.1Exploit: None knownExposed: 0

A fix is available — apply it.

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

drm/amdkfd: Fix an illegal memory access

In the kfd_wait_on_events() function, the kfd_event_waiter structure is allocated by alloc_event_waiters(), but the event field of the waiter structure is not initialized; When copy_from_user() fails in the kfd_wait_on_events() function, it will enter exception handling to release the previously allocated memory of the waiter structure; Due to the event field of the waiters structure being accessed in the free_waiters() function, this results in illegal memory access and system crash, here is the crash log:

localhost kernel: RIP: 0010:native_queued_spin_lock_slowpath+0x185/0x1e0 localhost kernel: RSP: 0018:ffffaa53c362bd60 EFLAGS: 00010082 localhost kernel: RAX: ff3d3d6bff4007cb RBX: 0000000000000282 RCX: 00000000002c0000 localhost kernel: RDX: ffff9e855eeacb80 RSI: 000000000000279c RDI: ffffe7088f6a21d0 localhost kernel: RBP: ffffe7088f6a21d0 R08: 00000000002c0000 R09: ffffaa53c362be64 localhost kernel: R10: ffffaa53c362bbd8 R11: 0000000000000001 R12: 0000000000000002 localhost kernel: R13: ffff9e7ead15d600 R14: 0000000000000000 R15: ffff9e7ead15d698 localhost kernel: FS: 0000152a3d111700(0000) GS:ffff9e855ee80000(0000) knlGS:0000000000000000 localhost kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 localhost kernel: CR2: 0000152938000010 CR3: 000000044d7a4000 CR4: 00000000003506e0 localhost kernel: Call Trace: localhost kernel: _raw_spin_lock_irqsave+0x30/0x40 localhost kernel: remove_wait_queue+0x12/0x50 localhost kernel: kfd_wait_on_events+0x1b6/0x490 [hydcu] localhost kernel: ? ftrace_graph_caller+0xa0/0xa0 localhost kernel: kfd_ioctl+0x38c/0x4a0 [hydcu] localhost kernel: ? kfd_ioctl_set_trap_handler+0x70/0x70 [hydcu] localhost kernel: ? kfd_ioctl_create_queue+0x5a0/0x5a0 [hydcu] localhost kernel: ? ftrace_graph_caller+0xa0/0xa0 localhost kernel: __x64_sys_ioctl+0x8e/0xd0 localhost kernel: ? syscall_trace_enter.isra.18+0x143/0x1b0 localhost kernel: do_syscall_64+0x33/0x80 localhost kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 localhost kernel: RIP: 0033:0x152a4dff68d7

Allocate the structure with kcalloc, and remove redundant 0-initialization and a redundant loop condition check.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
KEV
Not listed

Published

May 2, 2025

Last Modified

August 5, 2026

Advisory Details (7)

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

drm/amdkfd: Fix an illegal memory access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4fc8fff378b2f2039f2a666d9f8c570f4e58352c
generic

drm/amdkfd: Fix an illegal memory access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61f306f8df0d5559659c5578cf6d95236bcdcb25
generic

drm/amdkfd: Fix an illegal memory access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d9923e7214a870b312bf61f6a89c7554d0966985
generic

drm/amdkfd: Fix an illegal memory access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2fece63b55c5d74cd6f5de51159e2cde37e10555
generic

drm/amdkfd: Fix an illegal memory access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6936525142a015e854d0a23e9ad9ea0a28b3843d
generic

drm/amdkfd: Fix an illegal memory access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bbf5eada4334a96e3a204b2307ff5b14dc380b0b
generic

drm/amdkfd: Fix an illegal memory access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5a3fb3b745af0ce46ec2e0c8e507bae45b937334

Vendor Advisories for CVE-2023-53090(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 / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-513.5.1.el8_92023-11-14redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 4.19.279—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 17× in last 7d / 49× 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 113 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:20 UTCEG score recompute
  4. 2026-08-05 10:20 UTCVendor advisory
  5. 2026-08-05 10:20 UTCGHSA enrichment
  6. 2026-08-04 11:05 UTCEG score recompute
  7. 2026-08-04 11:05 UTCVendor advisory
  8. 2026-08-04 11:04 UTCGHSA enrichment
  9. 2026-08-04 10:36 UTCEPSS rescore
  10. 2026-08-04 09:44 UTCEG score recompute
  11. 2026-08-04 09:44 UTCVendor advisory
  12. 2026-08-04 09:43 UTCGHSA enrichment
  13. 2026-08-03 10:34 UTCEPSS rescore
  14. 2026-08-02 02:25 UTCEPSS rescore
  15. 2026-08-02 02:25 UTCEPSS rescore
  16. 2026-08-01 04:14 UTCEPSS rescore
  17. 2026-07-30 16:26 UTCEPSS rescore
  18. 2026-07-30 01:29 UTCEPSS rescore
  19. 2026-07-28 15:34 UTCEPSS rescore
  20. 2026-07-28 15:34 UTCEPSS rescore
  21. 2026-07-26 14:53 UTCEPSS rescore
  22. 2026-07-25 14:16 UTCEPSS rescore
  23. 2026-07-24 14:16 UTCEPSS rescore
  24. 2026-07-24 07:11 UTCOSV refresh
  25. 2026-07-23 14:16 UTCEPSS rescore
Show 75 more
  1. 2026-07-23 02:29 UTCEG score recompute
  2. 2026-07-22 23:16 UTCEG score recompute
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-22 14:07 UTCEPSS rescore
  5. 2026-07-21 15:23 UTCEPSS rescore
  6. 2026-07-20 17:06 UTCEPSS rescore
  7. 2026-07-19 14:30 UTCEPSS rescore
  8. 2026-07-19 14:29 UTCEPSS rescore
  9. 2026-07-18 10:03 UTCEPSS rescore
  10. 2026-07-18 10:03 UTCEPSS rescore
  11. 2026-07-16 17:01 UTCEPSS rescore
  12. 2026-07-15 16:56 UTCEPSS rescore
  13. 2026-07-15 01:59 UTCEPSS rescore
  14. 2026-07-15 01:59 UTCEPSS rescore
  15. 2026-07-13 22:28 UTCEPSS rescore
  16. 2026-07-13 22:28 UTCEPSS rescore
  17. 2026-07-13 06:11 UTCEPSS rescore
  18. 2026-07-12 05:45 UTCEPSS rescore
  19. 2026-07-12 05:45 UTCEPSS rescore
  20. 2026-07-11 08:26 UTCEPSS rescore
  21. 2026-07-09 19:08 UTCEPSS rescore
  22. 2026-07-08 15:13 UTCEPSS rescore
  23. 2026-07-07 13:45 UTCEPSS rescore
  24. 2026-07-07 13:44 UTCEPSS rescore
  25. 2026-07-07 02:51 UTCOSV refresh
  26. 2026-07-06 16:26 UTCEPSS rescore
  27. 2026-07-06 16:26 UTCEPSS rescore
  28. 2026-07-06 02:22 UTCEPSS rescore
  29. 2026-07-06 02:22 UTCEPSS rescore
  30. 2026-07-05 02:29 UTCEPSS rescore
  31. 2026-07-04 06:29 UTCEPSS rescore
  32. 2026-07-01 15:05 UTCEPSS rescore
  33. 2026-06-30 23:21 UTCEPSS rescore
  34. 2026-06-30 23:21 UTCEPSS rescore
  35. 2026-06-29 14:05 UTCEPSS rescore
  36. 2026-06-28 14:06 UTCEPSS rescore
  37. 2026-06-28 14:06 UTCEPSS rescore
  38. 2026-06-28 04:55 UTCEPSS rescore
  39. 2026-06-27 03:07 UTCEPSS rescore
  40. 2026-06-25 13:48 UTCEPSS rescore
  41. 2026-06-25 13:48 UTCEPSS rescore
  42. 2026-06-24 14:04 UTCEPSS rescore
  43. 2026-06-24 14:04 UTCEPSS rescore
  44. 2026-06-23 21:31 UTCEPSS rescore
  45. 2026-06-23 21:31 UTCEPSS rescore
  46. 2026-06-22 14:24 UTCEPSS rescore
  47. 2026-06-22 14:24 UTCEPSS rescore
  48. 2026-06-21 14:55 UTCEPSS rescore
  49. 2026-06-21 14:55 UTCEPSS rescore
  50. 2026-06-21 01:58 UTCEPSS rescore
  51. 2026-06-21 01:58 UTCEPSS rescore
  52. 2026-06-19 19:24 UTCEPSS rescore
  53. 2026-06-19 19:24 UTCEPSS rescore
  54. 2026-06-18 17:51 UTCEPSS rescore
  55. 2026-06-18 13:43 UTCOSV refresh
  56. 2026-06-17 17:51 UTCEPSS rescore
  57. 2026-06-16 17:51 UTCEPSS rescore
  58. 2026-06-16 17:51 UTCEPSS rescore
  59. 2026-06-15 17:47 UTCEPSS rescore
  60. 2026-06-14 23:16 UTCEPSS rescore
  61. 2026-06-13 22:59 UTCEPSS rescore
  62. 2026-06-13 22:59 UTCEPSS rescore
  63. 2026-06-12 23:11 UTCEPSS rescore
  64. 2026-06-10 22:17 UTCEPSS rescore
  65. 2026-06-10 13:21 UTCEPSS rescore
  66. 2026-06-08 14:16 UTCEPSS rescore
  67. 2026-06-08 14:16 UTCEPSS rescore
  68. 2026-06-07 15:24 UTCEPSS rescore
  69. 2026-06-07 15:24 UTCEPSS rescore
  70. 2026-06-06 13:46 UTCEPSS rescore
  71. 2026-06-06 13:46 UTCEPSS rescore
  72. 2026-06-05 22:46 UTCEPSS rescore
  73. 2026-06-05 22:46 UTCEPSS rescore
  74. 2026-06-05 06:09 UTCEPSS rescore
  75. 2026-06-05 06:09 UTCEPSS rescore

Frequently asked(5)

What is CVE-2023-53090?
CVE-2023-53090 is a high vulnerability published on May 2, 2025. In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Fix an illegal memory access In the kfdwaitonevents() function, the kfdevent_waiter structure is allocated by alloceventwaiters(), but the event field of the waiter structure is not initialized; When copyfromuser()…
When was CVE-2023-53090 disclosed?
CVE-2023-53090 was first published in the National Vulnerability Database on May 2, 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-53090 actively exploited?
CVE-2023-53090 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 90.0% of all scored CVEs.
What is the CVSS score of CVE-2023-53090?
CVE-2023-53090 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2023-53090?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53090, 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-53090

Explore →

Is Your Infrastructure Affected by CVE-2023-53090?

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

Start Free Scan →Browse All CVEs