cve/2024/CVE-2024-39293.md
2025-09-29 21:09:30 +02:00

20 lines
1.3 KiB
Markdown

### [CVE-2024-39293](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-39293)
![](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=2863d665ea41282379f108e4da6c8a2366ba66db%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=6.9%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:Revert "xsk: Support redirect to any socket bound to the same umem"This reverts commit 2863d665ea41282379f108e4da6c8a2366ba66db.This patch introduced a potential kernel crash when multiple napi instancesredirect to the same AF_XDP socket. By removing the queue_index check, it ispossible for multiple napi instances to access the Rx ring at the same time,which will result in a corrupted ring state which can lead to a crash whenflushing the rings in __xsk_flush(). This can happen when the linked list ofsockets to flush gets corrupted by concurrent accesses. A quick and small fixis not possible, so let us revert this for now.
### POC
#### Reference
No PoCs from references.
#### Github
- https://github.com/fkie-cad/nvd-json-data-feeds