cve/2024/CVE-2024-35880.md

### [CVE-2024-35880](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-35880)
![](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=09f7520048ea%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=09f7520048eaaee9709091cd2787966f807da7c5%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=5cf4f52e6d8a%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=5cf4f52e6d8aa2d3b7728f568abbf9d42a3af252%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=6.7%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:io_uring/kbuf: hold io_buffer_list reference over mmapIf we look up the kbuf, ensure that it doesn't get unregistered untilafter we're done with it. Since we're inside mmap, we cannot safely usethe io_uring lock. Rely on the fact that we can lookup the buffer listunder RCU now and grab a reference to it, preventing it from beingunregistered until we're done with it. The lookup returns theio_buffer_list directly with it referenced.

### POC

#### Reference
No PoCs from references.

#### Github
- https://github.com/xairy/linux-kernel-exploitation