CVE-2026-74276spi: xilinx: use FIFO occupancy register to determine buffer size

Description

In the Linux kernel, the following vulnerability has been resolved: spi: xilinx: use FIFO occupancy register to determine buffer size The method the driver uses to determine the size of the FIFO has a problem. What it currently does is this: It stops the SPI hardware and writes to the TX FIFO register until TX FIFO FULL asserts in the status register. But the hardware does not only have the FIFO, it also has a shift register which can hold a byte. This can be seen, when writing a byte to the FIFO (while the SPI hardware is stopped,) the TX FIFO EMPTY is still empty. So, if we have a FIFO size of 16 for example, the current method returns a 17. This is a problem, at least when using the driver in irq mode. The same size determined for the TX FIFO is also assumed for the RX FIFO. When a SPI transaction wants to write the amount of the FIFO size or more bytes, the following happens, for example with 16 bytes FIFO size: The driver stops the SPI hardware and writes 17 bytes to the TX FIFO and starts the SPI hardware and goes sleep. The hardware then shifts out 17 bytes (FIFO + shift register) and simultaneously reads bytes into the RX FIFO, but it only has 16 places, so it looses one byte. Then TX FIFO empty asserts, wakes the driver again, which has a fast path and reads 16 bytes from the RX FIFO, but before reading the last 17th byte (which is lost) it does this: sr = xspi->read_fn(xspi->regs + XSPI_SR_OFFSET); if (!(sr & XSPI_SR_RX_EMPTY_MASK)) { xilinx_spi_rx(xspi); rx_words--; } It reads the status register and checks if the RX FIFO is not empty. But it is empty in our case. So this check spins in a while loop forever locking the driver. This patch fixes the logic to determine the FIFO size.

Timeline

Scores

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

EPSS (exploitation in 30 days)

0.18% · top 93% of all CVEs (12 Nov 2026)

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

Affected products

• Linux · Linux

  • affected 4c9a761402d780b86b9b068aba4ef8e29ed15e99 – < 4ee65558a7fda463222f5edc631b6d7862218725
  • affected 4c9a761402d780b86b9b068aba4ef8e29ed15e99 – < e98f589d54068dfcc7da42d9b730e47b84e2991a
  • affected 4c9a761402d780b86b9b068aba4ef8e29ed15e99 – < 1fc6a6c0cc7796b0c1cf4eec3f0720f422f09273
  • affected 4c9a761402d780b86b9b068aba4ef8e29ed15e99 – < dfab0d4698a642bab9b895e2e6d240838cfe2cc6
  • affected 4c9a761402d780b86b9b068aba4ef8e29ed15e99 – < d7ccd8736b67550eca746ed7fa39a36016ff114b
  • affected 4c9a761402d780b86b9b068aba4ef8e29ed15e99 – < 1c9246a199e19b2fd36e94feed60e55f27103a4f
  • affected 4c9a761402d780b86b9b068aba4ef8e29ed15e99 – < d1944b71c18e7494756bff1a6f80c25be99eaecb
  • affected 4c9a761402d780b86b9b068aba4ef8e29ed15e99 – < 47f3b5365536e8c38f264824ab15fdb74454e066

• Linux · Linux

  • affected 4.0
  • unaffected < 4.0
  • unaffected 5.10.261 – ≤ 5.10.*
  • unaffected 5.15.212 – ≤ 5.15.*
  • unaffected 6.1.178 – ≤ 6.1.*
  • unaffected 6.6.145 – ≤ 6.6.*
  • unaffected 6.12.97 – ≤ 6.12.*
  • unaffected 6.18.40 – ≤ 6.18.*
  • unaffected 7.1.5 – ≤ 7.1.*
  • unaffected 7.2 – ≤ *

Sources

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

• CVE.org record (opens in a new tab)
• CVE List JSON (GitHub) (opens in a new tab)
• NVD (opens in a new tab)
• FIRST EPSS (opens in a new tab)
• EUVD EUVD-2026-59423 (opens in a new tab)
• OSV.dev (opens in a new tab)
• GitHub Advisories (opens in a new tab)
• CIRCL Vulnerability-Lookup (opens in a new tab)

Badge for a README or a ticket

[![CVE-2026-74276](https://cveledger.app/badge/CVE-2026-74276.svg)](https://cveledger.app/cve/CVE-2026-74276)

Record last updated 17 Aug 2026, 05:16 UTC.