CVE-2023-54020 Details
Description
In the Linux kernel, the following vulnerability has been resolved: dmaengine: sf-pdma: pdma_desc memory leak fix Commit b2cc5c465c2c ("dmaengine: sf-pdma: Add multithread support for a DMA channel") changed sf_pdma_prep_dma_memcpy() to unconditionally allocate a new sf_pdma_desc each time it is called. The driver previously recycled descs, by checking the in_use flag, only allocating additional descs if the existing one was in use. This logic was removed in commit b2cc5c465c2c ("dmaengine: sf-pdma: Add multithread support for a DMA channel"), but sf_pdma_free_desc() was not changed to handle the new behaviour. As a result, each time sf_pdma_prep_dma_memcpy() is called, the previous descriptor is leaked, over time leading to memory starvation: unreferenced object 0xffffffe008447300 (size 192): comm "irq/39-mchp_dsc", pid 343, jiffies 4294906910 (age 981.200s) hex dump (first 32 bytes): 00 00 00 ff 00 00 00 00 b8 c1 00 00 00 00 00 00 ................ 00 00 70 08 10 00 00 00 00 00 00 c0 00 00 00 00 ..p............. backtrace: [<00000000064a04f4>] kmemleak_alloc+0x1e/0x28 [<00000000018927a7>] kmem_cache_alloc+0x11e/0x178 [<000000002aea8d16>] sf_pdma_prep_dma_memcpy+0x40/0x112 Add the missing kfree() to sf_pdma_free_desc(), and remove the redundant in_use flag.
A memory leak vulnerability has been introduced in the Linux kernel's SF-PDMA DMA engine driver. This issue arises from a change made to the 'sf_pdma_prep_dma_memcpy()' function, which now unconditionally allocates a new 'sf_pdma_desc' descriptor each time it is called. Previously, the driver recycled descriptors by checking an 'in_use' flag and only allocating new ones when necessary. The removal of this logic, without corresponding updates to the 'sf_pdma_free_desc()' function, has led to a memory leak. Each call to 'sf_pdma_prep_dma_memcpy()' leaks the previously allocated descriptor, causing memory starvation over time.
The vulnerability has been fixed in the Linux kernel. Users should upgrade to the latest version where this fix has been applied.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 24, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/03fece43fa109beba7cc9948c02f5e2d1205d607 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/8bd5040bd43f2b5ba3c898b09a3197a0c7ace126 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/ad222c9af25e3f074c180e389b3477dce42afc4f | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/b02e07015a5ac7bbc029da931ae17914b8ae0339 | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 24, 2025 | New CVE Received | kernel.org |
Volerion