CVE-2026-23202
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.
Does this matter?
Lower severity and a low EPSS score (0.11%). Track it; it rarely justifies an emergency change on its own.
Description
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.
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.11% probability · 1th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-476
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/3bc293d5b56502068481478842f57b3d96e432c7Patch
- https://git.kernel.org/stable/c/6fd446178a610a48e80e5c5b487b0707cd01daacPatch
- https://git.kernel.org/stable/c/712cde8d916889e282727cdf304a43683adf899ePatch
- https://git.kernel.org/stable/c/762e2ce71c8f0238e9eaf05d14da803d9a24422fPatch
- https://git.kernel.org/stable/c/9fa4262a80f751d14a6a39d2c03f57db68da2618Patch
- https://git.kernel.org/stable/c/bf4528ab28e2bf112c3a2cdef44fd13f007781cdPatch
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.