cve/2024/CVE-2024-36953.md

20 lines
1.1 KiB
Markdown
Raw Permalink Normal View History

2025-09-29 21:09:30 +02:00
### [CVE-2024-36953](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-36953)
![](https://img.shields.io/static/v1?label=Product&message=Linux&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=4.7%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=7d450e2821710718fd6703e9c486249cee913bab%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=blue)
### Description
In the Linux kernel, the following vulnerability has been resolved:KVM: arm64: vgic-v2: Check for non-NULL vCPU in vgic_v2_parse_attr()vgic_v2_parse_attr() is responsible for finding the vCPU that matchesthe user-provided CPUID, which (of course) may not be valid. If the IDis invalid, kvm_get_vcpu_by_id() returns NULL, which isn't handledgracefully.Similar to the GICv3 uaccess flow, check that kvm_get_vcpu_by_id()actually returns something and fail the ioctl if not.
### POC
#### Reference
No PoCs from references.
#### Github
- https://github.com/fkie-cad/nvd-json-data-feeds