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.
Security readout for executives and security teams
Plain-English summary
CVE-2023-54020 is a Linux kernel memory leak in the sf-pdma DMA driver. Repeated DMA memcpy preparation can leak small descriptor allocations, eventually starving kernel memory. Business impact is likely availability-focused and hardware/driver-specific, not a general remote compromise based on the provided sources.
Executive priority
Treat as a targeted availability risk rather than a broad emergency. Prioritize patching Linux systems that use the affected DMA driver or embedded hardware platforms, while tracking vendor guidance for exact package fixes.
Technical view
The sf-pdma driver changed descriptor allocation behavior after multithread support, but sf_pdma_free_desc() did not free the newly allocated sf_pdma_desc objects. The upstream fix adds missing kfree() handling and removes the now-redundant in_use flag. The issue can accumulate leaked 192-byte objects during sf_pdma_prep_dma_memcpy() calls.
Likely exposure
Exposure is limited to Linux systems running affected kernel builds where the sf-pdma driver is present, enabled, and used by relevant DMA workloads. The source bundle lists Linux kernel versions and stable commits, but does not identify distributions, appliances, or cloud images.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked KEV. The described impact is memory starvation over time from repeated driver activity. No source in the bundle establishes a remote attack path or privilege boundary crossing.
Researcher notes
Evidence is strongest for root cause and fix location, but incomplete for exploitability, CVSS, and real-world affected deployments. Analysis should focus on reachability of sf_pdma_prep_dma_memcpy() on specific hardware and whether untrusted workloads can trigger sustained DMA activity.
Mitigation direction
Check vendor or distribution advisories for fixed kernel packages.
Upgrade to a kernel containing the referenced stable fixes.
Prioritize systems using sf-pdma-capable hardware or DMA-heavy workloads.
Reboot after kernel updates to ensure the fixed driver is loaded.
Monitor kernel memory pressure until patched.
Validation and detection
Inventory kernel versions against the CVE affected version data.
Confirm whether the sf-pdma driver is built, loaded, or used.
Review vendor kernel changelogs for the referenced stable commits.
Check kernel logs and monitoring for unexplained memory starvation.
Verify patched systems are running the updated kernel after reboot.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-54020 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 24, 2025, 10:55 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.