CVE-2026-23202: Linux kernel · spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in bf4528ab28e2bf112c3a2cdef44fd13f007781cd : update Linux kernel when convenient.
Data as of 26 Oct 2026, 11:20 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-06-10.
- Patch
- Available – fixed in bf4528ab28e2bf112c3a2cdef44fd13f007781cd, 762e2ce71c8f0238e9eaf05d14da803d9a24422f, 712cde8d916889e282727cdf304a43683adf899e +9
Exploitation evidence
Disclosed: evidence found.
CVE published 14 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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.
References
- git.kernel.org/stable/c/9fa4262a80f751d14a6a39d2c03f57db68da2618 (opens in a new tab)
- git.kernel.org/stable/c/762e2ce71c8f0238e9eaf05d14da803d9a24422f (opens in a new tab)
- git.kernel.org/stable/c/712cde8d916889e282727cdf304a43683adf899e (opens in a new tab)
- git.kernel.org/stable/c/6fd446178a610a48e80e5c5b487b0707cd01daac (opens in a new tab)
- git.kernel.org/stable/c/3bc293d5b56502068481478842f57b3d96e432c7 (opens in a new tab)
- git.kernel.org/stable/c/bf4528ab28e2bf112c3a2cdef44fd13f007781cd (opens in a new tab)