Medium · published February 14, 2026
In the Linux kernel, the following vulnerability has been resolved:
spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer
The curr_xfer field is read by the IRQ handler without holding the lock
to check if a transfer is in progress. When clearing curr_xfer in the
combined sequence transfer loop, protect it with the spinlock to prevent
a race with the interrupt handler.
Protect the curr_xfer clearing at the exit path of
tegra_qspi_combined_seq_xfer() with the spinlock to prevent a race
with the interrupt handler that reads this field.
Without this protection, the IRQ handler could read a partially updated
curr_xfer value, leading to NULL pointer dereference or use-after-free.
| Product | Versions | Fixed in |
|---|---|---|
| linux/linux_kernel | ≥ 5.15.198, < 5.15.200 | 5.15.200 |
| linux/linux_kernel | ≥ 6.1.160, < 6.1.163 | 6.1.163 |
| linux/linux_kernel | ≥ 6.6.120, < 6.6.124 | 6.6.124 |
| linux/linux_kernel | ≥ 6.12.63, < 6.12.70 | 6.12.70 |
| linux/linux_kernel | ≥ 6.17.13, < 6.18 | 6.18 |
| linux/linux_kernel | ≥ 6.18.2, < 6.18.10 | 6.18.10 |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |
| linux/linux_kernel | all versions | — |