LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23202: spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2026-23202 is a Linux kernel race condition in the tegra210-quad SPI driver. Under interrupt timing, the kernel may read transfer state while it is being cleared, potentially causing a crash or unsafe memory access. The source does not provide CVSS, confirmed exploitation, or business impact beyond kernel instability risk.

Executive priority

Treat as a targeted kernel stability issue unless your environment uses affected Tegra SPI functionality. Patch through normal kernel maintenance, with higher priority for embedded or appliance systems where kernel crashes affect service availability.

Technical view

The bug is in tegra_qspi_combined_seq_xfer(). curr_xfer is read by the IRQ handler without the same lock used when clearing it. The fix protects the exit-path clearing with a spinlock, preventing a race that could lead to NULL pointer dereference or use-after-free.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds with the tegra210-quad SPI driver present and relevant hardware or driver usage. The bundle lists Linux kernel version and commit identifiers, but no CPEs or distribution package mappings.

Exploitation context

The CVE is not marked KEV, and the provided sources do not claim active exploitation or public exploit availability. The described condition depends on interrupt timing during SPI transfer handling, suggesting reliability or denial-of-service concern, but exploitability is not fully evidenced.

Researcher notes

Evidence is limited to the Linux kernel fix description and stable commit references. No CVSS, CWE, CPE, exploit report, or downstream distribution advisory is included. Avoid broad exposure claims without confirming driver presence and vendor package mapping.

Mitigation direction

  • Update to a kernel containing one of the referenced stable fixes.
  • Check your Linux distribution advisory for mapped package versions.
  • Prioritize systems using the tegra210-quad SPI driver.
  • If patching is delayed, review vendor guidance for operational mitigations.

Validation and detection

  • Inventory kernels and compare against vendor fixed package guidance.
  • Check whether the tegra210-quad SPI driver is built, loaded, or required.
  • Review kernel logs for SPI, IRQ, NULL dereference, or use-after-free symptoms.
  • Confirm the referenced stable fix is present in deployed kernel source or changelog.
Prepared
Confidence
medium
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23202 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
7Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux88db8bb7ed1bb474618acdf05ebd4f0758d244e2, 83309dd551cfd60a5a1a98d9cab19f435b44d46d, c934e40246da2c5726d14e94719c514e30840df8, 551060efb156c50fe33799038ba8145418cfdeef, 01bbf25c767219b14c3235bfa85906b8d2cb8fbc, b4e002d8a7cee3b1d70efad0e222567f92a73000, bb0c58be84f907285af45657c1d4847b960a12bf, 6.17.13unaffected
LinuxLinux5.15.198, 6.1.160, 6.6.120, 6.12.63, 6.18.2unaffected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.