spi: tegra210-quad: Protect curr_xfer check in IRQ handler
Summary
| CVE | CVE-2026-23207 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-02-14 17:15:58 UTC |
| Updated | 2026-04-02 12:16:19 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: spi: tegra210-quad: Protect curr_xfer check in IRQ handler Now that all other accesses to curr_xfer are done under the lock, protect the curr_xfer NULL check in tegra_qspi_isr_thread() with the spinlock. Without this protection, the following race can occur: CPU0 (ISR thread) CPU1 (timeout path) ---------------- ------------------- if (!tqspi->curr_xfer) // sees non-NULL spin_lock() tqspi->curr_xfer = NULL spin_unlock() handle_*_xfer() spin_lock() t = tqspi->curr_xfer // NULL! ... t->len ... // NULL dereference! With this patch, all curr_xfer accesses are now properly synchronized. Although all accesses to curr_xfer are done under the lock, in tegra_qspi_isr_thread() it checks for NULL, releases the lock and reacquires it later in handle_cpu_based_xfer()/handle_dma_based_xfer(). There is a potential for an update in between, which could cause a NULL pointer dereference. To handle this, add a NULL check inside the handlers after acquiring the lock. This ensures that if the timeout path has already cleared curr_xfer, the handler will safely return without dereferencing the NULL pointer. |
Risk And Classification
Primary CVSS: v3.1 4.7 MEDIUM from [email protected]
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Problem Types: CWE-362 | CWE-416
CVSS v3.1 Breakdown
Attack Vector
LocalAttack Complexity
HighPrivileges Required
LowUser Interaction
NoneScope
UnchangedConfidentiality
NoneIntegrity
NoneAvailability
HighCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Operating System | Linux | Linux Kernel | All | All | All | All |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 551060efb156c50fe33799038ba8145418cfdeef 84e926c1c272a35ddb9b86842d32fa833a60dfc7 git | Not specified |
| CNA | Linux | Linux | affected 01bbf25c767219b14c3235bfa85906b8d2cb8fbc 2ac3a105e51496147c0e44e49466eecfcc532d57 git | Not specified |
| CNA | Linux | Linux | affected b4e002d8a7cee3b1d70efad0e222567f92a73000 edf9088b6e1d6d88982db7eb5e736a0e4fbcc09e git | Not specified |
| CNA | Linux | Linux | affected 88db8bb7ed1bb474618acdf05ebd4f0758d244e2 git | Not specified |
| CNA | Linux | Linux | affected 83309dd551cfd60a5a1a98d9cab19f435b44d46d git | Not specified |
| CNA | Linux | Linux | affected c934e40246da2c5726d14e94719c514e30840df8 git | Not specified |
| CNA | Linux | Linux | affected bb0c58be84f907285af45657c1d4847b960a12bf git | Not specified |
| CNA | Linux | Linux | affected 6.12.63 6.12.80 semver | Not specified |
| CNA | Linux | Linux | affected 6.18.2 6.18.10 semver | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/2ac3a105e51496147c0e44e49466eecfcc532d57 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/edf9088b6e1d6d88982db7eb5e736a0e4fbcc09e | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | Patch |
| git.kernel.org/stable/c/84e926c1c272a35ddb9b86842d32fa833a60dfc7 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.