Bug 2395369 (CVE-2023-53181) - CVE-2023-53181 kernel: dma-buf/dma-resv: Stop leaking on krealloc() failure
Summary: CVE-2023-53181 kernel: dma-buf/dma-resv: Stop leaking on krealloc() failure
Keywords:
Status: NEW
Alias: CVE-2023-53181
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-15 15:10 UTC by OSIDB Bzimport
Modified: 2025-10-06 10:50 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-09-15 15:10:13 UTC
In the Linux kernel, the following vulnerability has been resolved:

dma-buf/dma-resv: Stop leaking on krealloc() failure

Currently dma_resv_get_fences() will leak the previously
allocated array if the fence iteration got restarted and
the krealloc_array() fails.

Free the old array by hand, and make sure we still clear
the returned *fences so the caller won'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's
zero out *num_fences as well for good measure.


Note You need to log in before you can comment on or make changes to this bug.