CVE-2023-54020

dmaengine: sf-pdma: pdma_desc memory leak fix

N/A
Published: December 24, 2025 at 10:55 AM UTC
Updated: June 17, 2026 at 06:46 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.10.137v ≥ 5.18.18v ≥ 5.19.25.10.137 ≤ v < 5.115.15.61 ≤ v < 5.15.995.18.18 ≤ v < 5.195.19.2 ≤ v < 5.206.0 ≤ v < 6.1.166.0 ≤ v < 6.2.36.0 ≤ v < 6.34c7350b1dd8a192af844de32fc99b9e34c876fda5.10.1375.15.615.18.185.19.25ab2782c944e324008ef5d658f2494a9f0e3c5ac6.0a93b3f1e11971a91b6441b6d47488f4492cc113fb2cc5c465c2cb8ab697c3fd6583c614e3f6cfbccb9b4992f897be9b0b9e3a3b956cab6b75ccc3f11
Vendor states this is fixed in 03fece43fa109beba7cc9948c02f5e2d1205d607 (fixed)
Vendor states this is fixed in 8bd5040bd43f2b5ba3c898b09a3197a0c7ace126 (fixed)
Vendor states this is fixed in ad222c9af25e3f074c180e389b3477dce42afc4f (fixed)
Vendor states this is fixed in b02e07015a5ac7bbc029da931ae17914b8ae0339 (fixed)
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.15.99 (unaffected)
Affected range stops below 5.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.20, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.0 (unaffected)
Vendor states this is fixed in 6.1.16 (unaffected)
Vendor states this is fixed in 6.2.3 (unaffected)
Vendor states this is fixed in 6.3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card