# spi: tegra210-quad: Protect curr_xfer check in IRQ handler

CVE record · `CVE-2026-23207`

- **Identifiers:** `CVE-2026-23207`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 14 Feb 2026
- **Updated:** 5 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 14 Feb 2026, 16:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `83309dd551cfd60a5a1a98d9cab19f435b44d46d to before 8261fa3da6e9001be95a54b857df9759e9098d2f` (git)
  - affected: `c934e40246da2c5726d14e94719c514e30840df8 to before 513587caec66b67243027f26867ad3512f06744f` (git)
  - affected: `551060efb156c50fe33799038ba8145418cfdeef to before 84e926c1c272a35ddb9b86842d32fa833a60dfc7` (git)
  - affected: `01bbf25c767219b14c3235bfa85906b8d2cb8fbc to before 2ac3a105e51496147c0e44e49466eecfcc532d57` (git)
  - affected: `b4e002d8a7cee3b1d70efad0e222567f92a73000 to before edf9088b6e1d6d88982db7eb5e736a0e4fbcc09e` (git)
  - affected: `88db8bb7ed1bb474618acdf05ebd4f0758d244e2` (git)
  - affected: `bb0c58be84f907285af45657c1d4847b960a12bf` (git)
  - affected: `5.15.198 to before 5.16` (semver)
  - affected: `6.17.13 to before 6.18` (semver)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.1.160 to before 6.1.191` (semver)
  - affected: `6.6.120 to before 6.6.160` (semver)
  - affected: `6.12.63 to before 6.12.80` (semver)
  - affected: `6.18.2 to before 6.18.10` (semver)
  - Other versions: unaffected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel's spi tegra210-quad driver had a race in its interrupt handler where the current transfer pointer could be cleared by the timeout path between a NULL check and its use, leading to a NULL pointer dereference. The source gives few details on how an attacker would reach this condition. The fix adds the missing locking and a NULL check inside the handlers; affected kernel version ranges are listed in the source, and fixed versions are 6.1.191, 6.6.160, 6.12.80 and 6.18.10 for the respective stable branches. Upgrade to a fixed kernel version. No workaround is listed.

Written 12 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0013, the 2nd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 14 Feb 2026, 16:27 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-23207)
- 14 Feb 2026, 17:15 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-23207)

## Sources

- [CVE List: CVE-2026-23207](https://www.cve.org/CVERecord?id=CVE-2026-23207)
- [NVD: CVE-2026-23207](https://nvd.nist.gov/vuln/detail/CVE-2026-23207)

### References from the CNA

- <https://git.kernel.org/stable/c/8261fa3da6e9001be95a54b857df9759e9098d2f>
- <https://git.kernel.org/stable/c/513587caec66b67243027f26867ad3512f06744f>
- <https://git.kernel.org/stable/c/84e926c1c272a35ddb9b86842d32fa833a60dfc7>
- <https://git.kernel.org/stable/c/2ac3a105e51496147c0e44e49466eecfcc532d57>
- <https://git.kernel.org/stable/c/edf9088b6e1d6d88982db7eb5e736a0e4fbcc09e>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-23207>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-23207/>. Everything for agents: <https://agentprime.io/llms.txt>.
