Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-54020

dmaengine: sf-pdma: pdma_desc memory leak fix

Not scoredEPSS 0.19%
Published
Updated
Reserved
Assigned by
Linux

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.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (6 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 5ab2782c944e324008ef5d658f2494a9f0e3c5ac – < ad222c9af25e3f074c180e389b3477dce42afc4f
    • affected b2cc5c465c2cb8ab697c3fd6583c614e3f6cfbcc – < 03fece43fa109beba7cc9948c02f5e2d1205d607
    • affected b2cc5c465c2cb8ab697c3fd6583c614e3f6cfbcc – < 8bd5040bd43f2b5ba3c898b09a3197a0c7ace126
    • affected b2cc5c465c2cb8ab697c3fd6583c614e3f6cfbcc – < b02e07015a5ac7bbc029da931ae17914b8ae0339
    • affected b9b4992f897be9b0b9e3a3b956cab6b75ccc3f11
    • affected 4c7350b1dd8a192af844de32fc99b9e34c876fda
    • affected a93b3f1e11971a91b6441b6d47488f4492cc113f
    • affected 5.15.61 – < 5.15.99
    • affected 5.10.137 – < 5.11
    • affected 5.18.18 – < 5.19
    • affected 5.19.2 – < 5.20
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 5.15.99 – ≤ 5.15.*
    • unaffected 6.1.16 – ≤ 6.1.*
    • unaffected 6.2.3 – ≤ 6.2.*
    • unaffected 6.3 – ≤ *

References (4)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-54020 badge
[![CVE-2023-54020](https://trackcve.app/badge/CVE-2023-54020.svg)](https://trackcve.app/cve/CVE-2023-54020)

Record last updated .