CVE-2025-68746spi: tegra210-quad: Fix timeout handling
- 7.8HighCVSS base score
- 0.14%Exploitation in 30 daysEPSS · top 96% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
Published
- 10 months later
· 10 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Deferred | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.14% · top 96% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 921fc1838fb036f690b8ba52e6a6d3644b475cbb – < 88db8bb7ed1bb474618acdf05ebd4f0758d244e2
- affected 921fc1838fb036f690b8ba52e6a6d3644b475cbb – < 83309dd551cfd60a5a1a98d9cab19f435b44d46d
- affected 921fc1838fb036f690b8ba52e6a6d3644b475cbb – < c934e40246da2c5726d14e94719c514e30840df8
- affected 921fc1838fb036f690b8ba52e6a6d3644b475cbb – < 551060efb156c50fe33799038ba8145418cfdeef
- affected 921fc1838fb036f690b8ba52e6a6d3644b475cbb – < bb0c58be84f907285af45657c1d4847b960a12bf
- affected 921fc1838fb036f690b8ba52e6a6d3644b475cbb – < 01bbf25c767219b14c3235bfa85906b8d2cb8fbc
- affected 921fc1838fb036f690b8ba52e6a6d3644b475cbb – < b4e002d8a7cee3b1d70efad0e222567f92a73000
- affected 5.12
- unaffected < 5.12
- unaffected 5.15.198 – ≤ 5.15.*
- unaffected 6.1.160 – ≤ 6.1.*
- unaffected 6.6.120 – ≤ 6.6.*
- unaffected 6.12.63 – ≤ 6.12.*
- unaffected 6.17.13 – ≤ 6.17.*
- unaffected 6.18.2 – ≤ 6.18.*
- unaffected 6.19 – ≤ *
References
References7
- https://git.kernel.org/stable/c/88db8bb7ed1bb474618acdf05ebd4f0758d244e2 (opens in a new tab)
- https://git.kernel.org/stable/c/83309dd551cfd60a5a1a98d9cab19f435b44d46d (opens in a new tab)
- https://git.kernel.org/stable/c/c934e40246da2c5726d14e94719c514e30840df8 (opens in a new tab)
- https://git.kernel.org/stable/c/551060efb156c50fe33799038ba8145418cfdeef (opens in a new tab)
- https://git.kernel.org/stable/c/bb0c58be84f907285af45657c1d4847b960a12bf (opens in a new tab)
- https://git.kernel.org/stable/c/01bbf25c767219b14c3235bfa85906b8d2cb8fbc (opens in a new tab)
- https://git.kernel.org/stable/c/b4e002d8a7cee3b1d70efad0e222567f92a73000 (opens in a new tab)
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-2025-205216 (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
[](https://cveledger.app/cve/CVE-2025-68746)Record last updated .