Skip to content
Fencer Intel
medium 5.3

CVE-2023-52511 json

spi: sun6i: reduce DMA RX transfer width to single byte

published 2y ago modified 5mo ago also EUVD-2023-57136

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits
0
none known

Summary

In the Linux kernel, the following vulnerability has been resolved:

spi: sun6i: reduce DMA RX transfer width to single byte

Through empirical testing it has been determined that sometimes RX SPI transfers with DMA enabled return corrupted data. This is down to single or even multiple bytes lost during DMA transfer from SPI peripheral to memory. It seems the RX FIFO within the SPI peripheral can become confused when performing bus read accesses wider than a single byte to it during an active SPI transfer.

This patch reduces the width of individual DMA read accesses to the RX FIFO to a single byte to mitigate that issue.

Patch / fix

  • Linux Linux 5.15.134, 6.1.56, 6.5.6, 6.6
  • linux Debian 12 6.1.64-1
  • linux Debian 14, Debian 13 6.5.6-1

debian advisories DEBIAN-CVE-2023-52511

  • linux Ubuntu 22.04 LTS 5.15.0-94.104
  • linux-aws Ubuntu 22.04 LTS 5.15.0-1053.58
  • linux-gcp Ubuntu 22.04 LTS 5.15.0-1051.59
  • linux-gke Ubuntu 22.04 LTS 5.15.0-1050.55
  • linux-ibm Ubuntu 22.04 LTS 5.15.0-1046.49
  • linux-kvm Ubuntu 22.04 LTS 5.15.0-1050.55
  • linux-azure Ubuntu 22.04 LTS 5.15.0-1056.64
  • linux-gkeop Ubuntu 22.04 LTS 5.15.0-1036.42

ubuntu advisories UBUNTU-CVE-2023-52511

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-azure SLE Module for Public Cloud 15 SP5, openSUSE Leap 15.5 5.14.21-150500.33.48.1
  • kernel-syms-azure SLE Module for Public Cloud 15 SP5, openSUSE Leap 15.5 5.14.21-150500.33.48.1
  • kernel-source-azure SLE Module for Public Cloud 15 SP5, openSUSE Leap 15.5 5.14.21-150500.33.48.1
  • dtb-aarch64 openSUSE Leap 15.5 5.14.21-150500.55.59.1
  • kernel-64kb SLE Module for Basesystem 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.59.1
  • kernel-syms SLE Module for Development Tools 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.59.1
  • kernel-obs-qa openSUSE Leap 15.5 5.14.21-150500.55.59.1
  • kernel-source SLE Module for Development Tools 15 SP5, SLE Module for Basesystem 15 SP5, openSUSE Leap 15.5 5.14.21-150500.55.59.1

suse advisories SUSE-SU-2024:1490-1SUSE-SU-2024:1480-1SUSE-SU-2024:1466-1SUSE-SU-2024:1321-1SUSE-SU-2024:1320-1

Is CVE-2023-52511 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2023-52511 updated cvss 6.0

kernel: spi: sun6i: reduce DMA RX transfer width to single byte

  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-20).

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.