CVE-2026-23202
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.1% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.1% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.1% · EPSS, next 30 days
- Weakness
- CWE-476 · NULL pointer dereference
- Record status
- Modified
Affected
- Linux Kernel < 5.15.200
- Linux Kernel < 6.1.163
- Linux Kernel < 6.6.124
- Linux Kernel < 6.12.70
- Linux Kernel < 6.18
- Linux Kernel < 6.18.10
- Linux Kernel 6.19
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-23202.md and follow it. Check whether this project is affected by CVE-2026-23202. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/3bc293d5b56502068481478842f57b3d96e432c7
- https://git.kernel.org/stable/c/6fd446178a610a48e80e5c5b487b0707cd01daac
- https://git.kernel.org/stable/c/712cde8d916889e282727cdf304a43683adf899e
- https://git.kernel.org/stable/c/762e2ce71c8f0238e9eaf05d14da803d9a24422f
- https://git.kernel.org/stable/c/9fa4262a80f751d14a6a39d2c03f57db68da2618
- https://git.kernel.org/stable/c/bf4528ab28e2bf112c3a2cdef44fd13f007781cd
References
- https://git.kernel.org/stable/c/3bc293d5b56502068481478842f57b3d96e432c7
- https://git.kernel.org/stable/c/6fd446178a610a48e80e5c5b487b0707cd01daac
- https://git.kernel.org/stable/c/712cde8d916889e282727cdf304a43683adf899e
- https://git.kernel.org/stable/c/762e2ce71c8f0238e9eaf05d14da803d9a24422f
- https://git.kernel.org/stable/c/9fa4262a80f751d14a6a39d2c03f57db68da2618
- https://git.kernel.org/stable/c/bf4528ab28e2bf112c3a2cdef44fd13f007781cd