CVE-2025-68746: spi: tegra210-quad: Fix timeout handling
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 01bbf25c767219b14c3235bfa85906b8d2cb8fbc, 551060efb156c50fe33799038ba8145418cfdeef, 83309dd551cfd60a5a1a98d9cab19f435b44d46d; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1.
Low priority for now. Upgrade to Linux Linux 01bbf25c767219b14c3235bfa85906b8d2cb8fbc, 551060efb156c50fe33799038ba8145418cfdeef, 83309dd551cfd60a5a1a98d9cab19f435b44d46d; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Dec 24, 2025
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- —
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.12affected
- 921fc1838fb036f690b8ba52e6a6d3644b475cbb and later · before 88db8bb7ed1bb474618acdf05ebd4f0758d244e2affected · git
- 921fc1838fb036f690b8ba52e6a6d3644b475cbb and later · before 83309dd551cfd60a5a1a98d9cab19f435b44d46daffected · git
- 921fc1838fb036f690b8ba52e6a6d3644b475cbb and later · before c934e40246da2c5726d14e94719c514e30840df8affected · git
- 921fc1838fb036f690b8ba52e6a6d3644b475cbb and later · before 551060efb156c50fe33799038ba8145418cfdeefaffected · git
- 921fc1838fb036f690b8ba52e6a6d3644b475cbb and later · before bb0c58be84f907285af45657c1d4847b960a12bfaffected · git
- 921fc1838fb036f690b8ba52e6a6d3644b475cbb and later · before 01bbf25c767219b14c3235bfa85906b8d2cb8fbcaffected · git
- 921fc1838fb036f690b8ba52e6a6d3644b475cbb and later · before b4e002d8a7cee3b1d70efad0e222567f92a73000affected · git
- before 5.12not affected · semver
- 5.15.198 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.162-1 | 6.1.162-1 |
| Debian:13 | linux | before 6.12.63-1 | 6.12.63-1 |
| Debian:14 | linux | before 6.17.13-1 | 6.17.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-68744Dec 24, 2025 · bpf: Free special fields when update [lru_,]percpu_hash maps0Monitor
- ← EarlierCVE-2025-68745Dec 24, 2025 · scsi: qla2xxx: Clear cmds after chip reset39Monitor
- Later →CVE-2025-68747Dec 24, 2025 · drm/panthor: Fix UAF on kernel BO VA nodes31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 01bbf25c767219b14c3235bfa85906b8d2cb8fbc | Vendor (CNA) |
| Linux Linux | 551060efb156c50fe33799038ba8145418cfdeef | Vendor (CNA) |
| Linux Linux | 83309dd551cfd60a5a1a98d9cab19f435b44d46d | Vendor (CNA) |
| Linux Linux | 88db8bb7ed1bb474618acdf05ebd4f0758d244e2 | Vendor (CNA) |
| Linux Linux | b4e002d8a7cee3b1d70efad0e222567f92a73000 | Vendor (CNA) |
| Linux Linux | bb0c58be84f907285af45657c1d4847b960a12bf | Vendor (CNA) |
| Linux Linux | c934e40246da2c5726d14e94719c514e30840df8 | Vendor (CNA) |
| azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 | 6.6.121.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.162-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/551060efb156c50fe33799038ba8145418cfdeef
- git.kernel.org/stable/c/83309dd551cfd60a5a1a98d9cab19f435b44d46d
- git.kernel.org/stable/c/88db8bb7ed1bb474618acdf05ebd4f0758d244e2
- git.kernel.org/stable/c/b4e002d8a7cee3b1d70efad0e222567f92a73000
- git.kernel.org/stable/c/bb0c58be84f907285af45657c1d4847b960a12bf
- git.kernel.org/stable/c/c934e40246da2c5726d14e94719c514e30840df8
Vendor advisories and official records. Exploit/PoC links are deliberately left out.