{"uuid": "2ace1f50-92e5-4579-92dc-f48d45c1e68c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-56712", "type": "seen", "source": "https://t.me/cvedetector/13864", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-56712 - Linux udmabuf Memory Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-56712 \nPublished : Dec. 29, 2024, 9:15 a.m. | 24\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nudmabuf: fix memory leak on last export_udmabuf() error path  \n  \nIn export_udmabuf(), if dma_buf_fd() fails because the FD table is full, a  \ndma_buf owning the udmabuf has already been created; but the error handling  \nin udmabuf_create() will tear down the udmabuf without doing anything about  \nthe containing dma_buf.  \n  \nThis leaves a dma_buf in memory that contains a dangling pointer; though  \nthat doesn't seem to lead to anything bad except a memory leak.  \n  \nFix it by moving the dma_buf_fd() call out of export_udmabuf() so that we  \ncan give it different error handling.  \n  \nNote that the shape of this code changed a lot in commit 5e72b2b41a21  \n(\"udmabuf: convert udmabuf driver to use folios\"); but the memory leak  \nseems to have existed since the introduction of udmabuf. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"29 Dec 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-12-29T10:41:11.000000Z"}