CVE-2023-52517

linux: In the Linux kernel, the following vulnerability has been resolved: spi: sun6i: fix race between DMA RX transfer com...

CVE-2023-52517 is fixed in linux on 1 platform, first by DEBIAN-CVE-2023-52517, released March 2, 2024. It is not reported as exploited. Patch Radar priority: High.

High
CVSS
7.0
high
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0018
7th percentile

In the Linux kernel, the following vulnerability has been resolved: spi: sun6i: fix race between DMA RX transfer completion and RX FIFO drain Previously the transfer complete IRQ immediately drained to RX FIFO to read any data remaining in FIFO to the RX buffer. This behaviour is correct when dealing with SPI in interrupt mode. However in DMA mode the transfer complete interrupt still fires as soon as all bytes to be transferred have been stored in the FIFO. At that point data in the FIFO still needs to be picked up by the DMA engine. Thus the drain procedure and DMA engine end up racing to read from RX FIFO, corrupting any data read. Additionally the RX buffer pointer is never adjusted according to DMA progress in DMA mode, thus calling the RX FIFO drain procedure in DMA mode is a bug. Fix corruptions in DMA RX mode by draining RX FIFO only in interrupt mode. Also wait for completion of RX DMA when in DMA mode before returning to ensure all data has been copied to the supplied memory buffer.

Where it's fixed

ProductFixed inFixReleased
Linux
linux · Debian 12.15 (bookworm) 6.1.64-1 DEBIAN-CVE-2023-52517 Mar 2, 2024
linux · Debian 13.5 (trixie) 6.5.6-1 DEBIAN-CVE-2023-52517 Mar 2, 2024
linux · Debian 14 6.5.6-1 DEBIAN-CVE-2023-52517 Mar 2, 2024

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.