https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 04:09:30 +0000 https://vulnerability.circl.lu/vuln/cve-2023-53181 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dma-buf/dma-resv: Stop leaking on krealloc() failure</p> <p>Currently dma_resv_get_fences() will leak the previously allocated array if the fence iteration got restarted and the krealloc_array() fails.</p> <p>Free the old array by hand, and make sure we still clear the returned *fences so the caller won&#39;t end up accessing freed memory. Some (but not all) of the callers of dma_resv_get_fences() seem to still trawl through the array even when dma_resv_get_fences() failed. And let&#39;s zero out *num_fences as well for good measure.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>dma-buf/dma-resv: Stop leaking on krealloc() failure</p> <p>Currently dma_resv_get_fences() will leak the previously allocated array if the fence iteration got restarted and the krealloc_array() fails.</p> <p>Free the old array by hand, and make sure we still clear the returned *fences so the caller won&#39;t end up accessing freed memory. Some (but not all) of the callers of dma_resv_get_fences() seem to still trawl through the array even when dma_resv_get_fences() failed. And let&#39;s zero out *num_fences as well for good measure.</p> https://vulnerability.circl.lu/vuln/cve-2023-53181