LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A timing race in Linux’s NVIDIA Tegra210 QSPI driver can leave the kernel referencing stale memory after a transfer timeout. A locally authenticated, low-privilege attacker may be able to trigger serious confidentiality, integrity, or availability impact, although the supplied evidence does not describe a proven exploitation method or observed attacks.

Executive priority

Prioritize remediation for Tegra systems that actively use QSPI and permit local untrusted users or workloads. Other Linux systems are lower priority pending exposure verification. Treat this as a focused high-severity kernel issue, not a universal Linux emergency.

Technical view

If the threaded QSPI interrupt handler is delayed by a busy CPU, timeout cleanup can fail the pending message while leaving curr_xfer pointing to stale memory. A later IRQ thread may access that pointer. The stable fixes clear curr_xfer on timeout, validate it in the IRQ thread, and clear interrupts after failure.

Likely exposure

Exposure is limited to Linux systems using the tegra210-quad SPI/QSPI driver on relevant hardware. The supplied affected-version data is ambiguous and should not be treated as definitive fixed-version guidance. Systems without this driver or hardware are unlikely to be exposed.

Exploitation context

The CVSS 3.1 score is 7.8 with local access and low privileges required. Triggering depends on unusual interrupt-thread delay and transfer-timeout timing. The source bundle marks KEV false and provides no evidence of active exploitation or a public exploit.

Researcher notes

This is a timeout-versus-threaded-IRQ race producing a stale curr_xfer reference. The fixes add pointer invalidation, an IRQ-side validity check, and interrupt clearing on failure. The description notes that moving interrupt clearing into a hard IRQ handler would be a more involved design improvement. Exact consequences and reproducibility are not established in the supplied sources.

Mitigation direction

  • Obtain the applicable patched kernel from the system or distribution vendor.
  • Confirm the update incorporates the relevant Linux stable fix for CVE-2025-68746.
  • Prioritize systems actively using the tegra210-quad QSPI driver.
  • Consult vendor guidance before relying on version numbers from the supplied affected-version data.

Validation and detection

  • Inventory Tegra-based Linux systems and determine whether the tegra210-quad driver is loaded or built in.
  • Record running kernel versions, distribution builds, and applicable vendor security advisories.
  • Verify the installed kernel source or package includes the appropriate referenced stable commit.
  • Monitor affected systems for QSPI transfer failures, kernel warnings, crashes, or unexpected interrupt behavior.
Prepared
Confidence
medium
Sources
9

Public sources used

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-2025-68746 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-68746Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux921fc1838fb036f690b8ba52e6a6d3644b475cbb, 921fc1838fb036f690b8ba52e6a6d3644b475cbb, 921fc1838fb036f690b8ba52e6a6d3644b475cbb, 921fc1838fb036f690b8ba52e6a6d3644b475cbb, 921fc1838fb036f690b8ba52e6a6d3644b475cbb, 921fc1838fb036f690b8ba52e6a6d3644b475cbb, 921fc1838fb036f690b8ba52e6a6d3644b475cbbunaffected
LinuxLinux5.12, 0, 5.15.198, 6.1.160, 6.6.120, 6.12.63, 6.17.13, 6.18.2, 6.19affected
Weakness

CWE details

No CWE listed

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