cve/2024/CVE-2024-56712.md

21 lines
1.5 KiB
Markdown
Raw Normal View History

2025-09-29 16:08:36 +00:00
### [CVE-2024-56712](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-56712)
![](https://img.shields.io/static/v1?label=Product&message=Linux&color=blue)
2025-09-29 21:09:30 +02:00
![](https://img.shields.io/static/v1?label=Version&message=&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=4.20%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Version&message=fbb0de795078190a9834b3409e4b009cfb18a6d4%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=blue)
2025-09-29 16:08:36 +00:00
### Description
In the Linux kernel, the following vulnerability has been resolved:udmabuf: fix memory leak on last export_udmabuf() error pathIn export_udmabuf(), if dma_buf_fd() fails because the FD table is full, adma_buf owning the udmabuf has already been created; but the error handlingin udmabuf_create() will tear down the udmabuf without doing anything aboutthe containing dma_buf.This leaves a dma_buf in memory that contains a dangling pointer; thoughthat doesn't seem to lead to anything bad except a memory leak.Fix it by moving the dma_buf_fd() call out of export_udmabuf() so that wecan give it different error handling.Note that the shape of this code changed a lot in commit 5e72b2b41a21("udmabuf: convert udmabuf driver to use folios"); but the memory leakseems to have existed since the introduction of udmabuf.
### POC
#### Reference
No PoCs from references.
#### Github
- https://github.com/cku-heise/euvd-api-doc
2025-09-29 21:09:30 +02:00
- https://github.com/fkie-cad/nvd-json-data-feeds
2025-09-29 16:08:36 +00:00