high CVSS 7

CVE-2023-52517·Kernel vulnerability

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.

Severity
high
Software
Kernel
Fixed in
6.5.6
Published
2024-03-02

Affected versions

From: 6.2

Until: 6.5.6

Fixed in: 6.5.6

How to fix this CVE

Update your Linux kernel to version 6.5.6 or later to resolve a critical race condition in the sun6i SPI driver's DMA handling. This vulnerability causes data corruption during DMA-based SPI transfers by introducing a race between the transfer completion interrupt and the DMA engine when reading from the RX FIFO. Immediate patching is recommended for systems using sun6i SPI controllers with DMA mode enabled.

sudo dnf update kernel kernel-devel

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check installed kernel version with `uname -r` and compare against affected range 6.2 to 6.5.5
  2. Step 2: Verify sun6i SPI driver is loaded with `lsmod | grep sun6i` or check `cat /proc/modules | grep spi`
  3. Step 3: Check kernel logs for SPI DMA-related errors with `dmesg | grep -i 'spi\|dma' | tail -50` and look for corruption warnings or data inconsistencies
  4. Step 4: After patching to 6.5.6+, verify with `uname -r` and reboot if necessary, then re-check logs to confirm no SPI DMA errors persist

FAQ

What is CVE-2023-52517?

CVE-2023-52517 is a race condition vulnerability in the Linux kernel's sun6i SPI driver where the transfer completion interrupt handler attempts to drain the RX FIFO at the same time the DMA engine is reading from it, resulting in corrupted SPI data during DMA transfers.

Is CVE-2023-52517 being actively exploited?

No, CVE-2023-52517 is not listed in CISA's Known Exploited Vulnerabilities catalog and no public exploits are currently available. However, it causes silent data corruption on affected systems.

What versions of Kernel are affected by CVE-2023-52517?

Linux kernel versions 6.2 through 6.5.5 are vulnerable. Version 6.5.6 and later contain the fix.

How do I check if my server is vulnerable to CVE-2023-52517?

Run `uname -r` to check your kernel version. If it shows a version between 6.2 and 6.5.5 and `lsmod | grep sun6i` returns results, your system is vulnerable.

Does Defensia detect CVE-2023-52517?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2023-52517 will appear in your dashboard with remediation steps.

Related Kernel CVEs

CVE-2024-42256CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: cifs: Fix server re-repick on subrequest retry When a subrequest is marked for needing retry, netfs will call cifs_prepare_write() which will make cifs repick the server for the op before renegotiating credits; it then calls cifs_issue_write() which invokes smb2_async_writev() - which re-repicks the server. If a different server is then selected, this causes the increment of server->in_flight to happen against one record and the decrement to happen against another, leading to misaccounting. Fix this by just removing the repick code in smb2_async_writev(). As this is only called from netfslib-driven code, cifs_prepare_write() should always have been called first, and so server should never be NULL and the preparatory step is repeated in the event that we do a retry. The problem manifests as a warning looking something like: WARNING: CPU: 4 PID: 72896 at fs/smb/client/smb2ops.c:97 smb2_add_credits+0x3f0/0x9e0 [cifs] ... RIP: 0010:smb2_add_credits+0x3f0/0x9e0 [cifs] ... smb2_writev_callback+0x334/0x560 [cifs] cifs_demultiplex_thread+0x77a/0x11b0 [cifs] kthread+0x187/0x1d0 ret_from_fork+0x34/0x60 ret_from_fork_asm+0x1a/0x30 Which may be triggered by a number of different xfstests running against an Azure server in multichannel mode. generic/249 seems the most repeatable, but generic/215, generic/249 and generic/308 may also show it.
CVE-2024-36031CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: keys: Fix overwrite of key expiration on instantiation The expiry time of a key is unconditionally overwritten during instantiation, defaulting to turn it permanent. This causes a problem for DNS resolution as the expiration set by user-space is overwritten to TIME64_MAX, disabling further DNS updates. Fix this by restoring the condition that key_set_expiry is only called when the pre-parser sets a specific expiry.
CVE-2024-38612CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ipv6: sr: fix invalid unregister error path The error path of seg6_init() is wrong in case CONFIG_IPV6_SEG6_LWTUNNEL is not defined. In that case if seg6_hmac_init() fails, the genl_unregister_family() isn't called. This issue exist since commit 46738b1317e1 ("ipv6: sr: add option to control lwtunnel support"), and commit 5559cea2d5aa ("ipv6: sr: fix possible use-after-free and null-ptr-deref") replaced unregister_pernet_subsys() with genl_unregister_family() in this error path.
CVE-2024-38623CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Use variable length array instead of fixed size Should fix smatch warning: ntfs_set_label() error: __builtin_memcpy() 'uni->name' too small (20 vs 256)
CVE-2021-47548CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port() The if statement: if (port >= DSAF_GE_NUM) return; limits the value of port less than DSAF_GE_NUM (i.e., 8). However, if the value of port is 6 or 7, an array overflow could occur: port_rst_off = dsaf_dev->mac_cb[port]->port_rst_off; because the length of dsaf_dev->mac_cb is DSAF_MAX_PORT_NUM (i.e., 6). To fix this possible array overflow, we first check port and if it is greater than or equal to DSAF_MAX_PORT_NUM, the function returns.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2023-52517. Free for 1 server.

Get started free