Linux Kernel on 32-bit KVM arch/x86/kvm/x86.c kvm_vcpu_ioctl_x86_get_debugregs initialization

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Linux Kernel on 32-bit and classified as problematic. This vulnerability affects the function kvm_vcpu_ioctl_x86_get_debugregs of the file arch/x86/kvm/x86.c of the component KVM. This manipulation causes initialization.
This vulnerability is registered as CVE-2023-1513. The attack needs to be launched locally. No exploit is available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Linux Kernel on 32-bit (Operating System) (the affected version unknown). It has been declared as problematic. Affected by this vulnerability is the function kvm_vcpu_ioctl_x86_get_debugregs of the file arch/x86/kvm/x86.c of the component KVM. The manipulation with an unknown input leads to a initialization vulnerability. The CWE definition for the vulnerability is CWE-665. The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used. As an impact it is known to affect confidentiality. The summary by CVE is:
A flaw was found in KVM. When calling the KVM_GET_DEBUGREGS ioctl, on 32-bit systems, there might be some uninitialized portions of the kvm_debugregs structure that could be copied to userspace, causing an information leak.
The weakness was published 03/24/2023 as 2c10b61421a28e95a46ab489fd56c0f442ff6952. The advisory is shared at github.com. This vulnerability is known as CVE-2023-1513 since 03/20/2023. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 239841 (TencentOS Server 4: kernel (TSSA-2024:0960)), which helps to determine the existence of the flaw in a target environment.
Applying the patch 2c10b61421a28e95a46ab489fd56c0f442ff6952 is able to eliminate this problem. The bugfix is ready for download at github.com.
The vulnerability is also documented in the databases at Tenable (239841) and EUVD (EUVD-2023-23760). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 3.3
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: InitializationCWE: CWE-665
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 239841
Nessus Name: TencentOS Server 4: kernel (TSSA-2024:0960)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 2c10b61421a28e95a46ab489fd56c0f442ff6952
Timeline
03/20/2023 🔍03/24/2023 🔍
03/24/2023 🔍
08/11/2025 🔍
Sources
Vendor: kernel.orgAdvisory: 2c10b61421a28e95a46ab489fd56c0f442ff6952
Status: Confirmed
CVE: CVE-2023-1513 (🔍)
GCVE (CVE): GCVE-0-2023-1513
GCVE (VulDB): GCVE-100-223765
EUVD: 🔍
Entry
Created: 03/24/2023 07:21Updated: 08/11/2025 08:08
Changes: 03/24/2023 07:21 (45), 04/13/2023 22:19 (9), 06/19/2025 20:57 (17), 08/11/2025 08:08 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.