cve/2024/CVE-2024-50115.md

### [CVE-2024-50115](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-50115)
![](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=3.2%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=e4e517b4be019787ada4cbbce2f04570c21b0cbd%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: nSVM: Ignore nCR3[4:0] when loading PDPTEs from memoryIgnore nCR3[4:0] when loading PDPTEs from memory for nested SVM, as bits4:0 of CR3 are ignored when PAE paging is used, and thus VMRUN doesn'tenforce 32-byte alignment of nCR3.In the absolute worst case scenario, failure to ignore bits 4:0 can resultin an out-of-bounds read, e.g. if the target page is at the end of amemslot, and the VMM isn't using guard pages.Per the APM:  The CR3 register points to the base address of the page-directory-pointer  table. The page-directory-pointer table is aligned on a 32-byte boundary,  with the low 5 address bits 4:0 assumed to be 0.And the SDM's much more explicit:  4:0    IgnoredNote, KVM gets this right when loading PDPTRs, it's only the nSVM flowthat is broken.

### POC

#### Reference
No PoCs from references.

#### Github
- https://github.com/w4zu/Debian_security