CVE-2026-23207
Race Condition in Linux Tegra210 QSPI Causes NULL Pointer Dereference
Publication date: 2026-02-14
Last updated on: 2026-04-02
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.17.13 (inc) to 6.18 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 6.18.2 (inc) to 6.18.10 (exc) |
| linux | linux_kernel | From 5.15.198 (inc) to 5.16 (exc) |
| linux | linux_kernel | From 6.1.160 (inc) to 6.2 (exc) |
| linux | linux_kernel | From 6.12.63 (inc) to 6.13 (exc) |
| linux | linux_kernel | From 6.6.120 (inc) to 6.7 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
| CWE-362 | The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's tegra210-quad SPI driver, specifically in the handling of the curr_xfer variable within an interrupt request (IRQ) handler.
The issue arises because curr_xfer is accessed without proper synchronization in the tegra_qspi_isr_thread() function. While other accesses to curr_xfer are protected by a spinlock, this function checks curr_xfer for NULL without holding the lock, then releases and reacquires the lock later. This creates a race condition where curr_xfer could be set to NULL by another CPU thread between these operations.
As a result, the handler might dereference a NULL pointer, leading to a potential kernel crash or undefined behavior.
The fix involves protecting the NULL check of curr_xfer with the spinlock and adding an additional NULL check inside the handlers after acquiring the lock to prevent dereferencing NULL pointers.
How can this vulnerability impact me? :
This vulnerability can cause a NULL pointer dereference in the Linux kernel's SPI driver, which may lead to a kernel crash or system instability.
Such crashes can result in denial of service (DoS) conditions, potentially disrupting normal operation of devices using the affected driver.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is caused by a race condition in the Linux kernel's tegra210-quad SPI driver related to unsynchronized access to the curr_xfer pointer.
To mitigate this vulnerability, ensure that your Linux kernel includes the patch that protects all accesses to curr_xfer with the appropriate spinlock, especially adding a NULL check inside the handlers after acquiring the lock.
If you are using the affected NVIDIA tegra210-quad hardware, update your kernel to a version that contains this fix to prevent NULL pointer dereference due to the race condition.