CVE-2023-53205

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-09-15. 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:

KVM: s390/diag: fix racy access of physical cpu number in diag 9c handler

We do check for target CPU == -1, but this might change at the time we are going to use it. Hold the physical target CPU in a local variable to avoid out-of-bound accesses to the cpu arrays.

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

Published

September 15, 2025

Last Modified

August 5, 2026

Advisory Details (4)

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

KVM: s390/diag: fix racy access of physical cpu number in diag 9c handler - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: s390/diag: fix racy access of physical cpu number in diag 9c handler - kernel/git/stable/linux.git - Linux kernel stable tree

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

KVM: s390/diag: fix racy access of physical cpu number in diag 9c handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/86bfb18bad60fc468e5f112cbbd918462a8dd435
generic

KVM: s390/diag: fix racy access of physical cpu number in diag 9c handler - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0bc380beb78aa352eadbc21d934dd9606fcee808

Vendor Advisories for CVE-2023-53205(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-553.el8_102024-05-22redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 5.15.121osv

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 / 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 114 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2023-53205?
CVE-2023-53205 is a high vulnerability published on September 15, 2025. In the Linux kernel, the following vulnerability has been resolved: KVM: s390/diag: fix racy access of physical cpu number in diag 9c handler We do check for target CPU == -1, but this might change at the time we are going to use it. Hold the physical target CPU in a local variable to avoid…
When was CVE-2023-53205 disclosed?
CVE-2023-53205 was first published in the National Vulnerability Database on September 15, 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-53205 actively exploited?
CVE-2023-53205 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 94.9% of all scored CVEs.
What is the CVSS score of CVE-2023-53205?
CVE-2023-53205 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-53205?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-53205, 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-53205

Explore →

Is Your Infrastructure Affected by CVE-2023-53205?

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