CVE-2023-54020

Unknown

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.

SeverityUnknown
CVSS—
Exploit probability—
ProductLinux
PublishedDec 24, 2025
First seenDec 24, 2025

How to fix

Update
  • Linux Linuxad222c9af25e3f074c180e389b3477dce42afc4f, 03fece43fa109beba7cc9948c02f5e2d1205d607, 8bd5040bd43f2b5ba3c898b09a3197a0c7ace126, b02e07015a5ac7bbc029da931ae17914b8ae0339, 5.15.99, 5.11, 5.19, 5.20 or later

Affected products

ProductAffected versionsFixed in
Linux Linux5ab2782c944e324008ef5d658f2494a9f0e3c5ac ≤ v < ad222c9af25e3f074c180e389b3477dce42afc4f, b2cc5c465c2cb8ab697c3fd6583c614e3f6cfbcc ≤ v < 03fece43fa109beba7cc9948c02f5e2d1205d607, b2cc5c465c2cb8ab697c3fd6583c614e3f6cfbcc ≤ v < 8bd5040bd43f2b5ba3c898b09a3197a0c7ace126, b2cc5c465c2cb8ab697c3fd6583c614e3f6cfbcc ≤ v < b02e07015a5ac7bbc029da931ae17914b8ae0339, b9b4992f897be9b0b9e3a3b956cab6b75ccc3f11, 4c7350b1dd8a192af844de32fc99b9e34c876fda, a93b3f1e11971a91b6441b6d47488f4492cc113f, 5.15.61 ≤ v < 5.15.99, 5.10.137 ≤ v < 5.11, 5.18.18 ≤ v < 5.19, 5.19.2 ≤ v < 5.20, 6.0ad222c9af25e3f074c180e389b3477dce42afc4f, 03fece43fa109beba7cc9948c02f5e2d1205d607, 8bd5040bd43f2b5ba3c898b09a3197a0c7ace126, b02e07015a5ac7bbc029da931ae17914b8ae0339, 5.15.99, 5.11, 5.19, 5.20

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.