CVE-2023-53205
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-15

Last updated on: 2025-12-04

Assigner: kernel.org

Description
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 Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-15
Last Modified
2025-12-04
Generated
2026-06-16
AI Q&A
2025-09-15
EPSS Evaluated
2026-06-14
NVD
CVE-2023-53205
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
linux linux_kernel From 5.13 (inc) to 5.15.121 (exc)
linux linux_kernel From 5.16 (inc) to 6.1.39 (exc)
linux linux_kernel From 6.2 (inc) to 6.4.4 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-787 The product writes data past the end, or before the beginning, of the intended buffer.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is a race condition in the Linux kernel's KVM s390 architecture diagnostic 9c handler. It involves a racy access to the physical CPU number, where the target CPU value might change between the check and its use, potentially causing out-of-bound accesses to CPU arrays. The fix involves holding the physical target CPU in a local variable to prevent this issue.

Impact Analysis

The vulnerability could lead to out-of-bound accesses in the kernel's CPU arrays, which may cause system instability, crashes, or potentially allow unintended behavior in the kernel's virtualization subsystem on s390 architectures.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2023-53205. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart