CVE-2026-23202: spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer

Published Feb 14, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

spi: tegra210-quad: Protect currxfer in tegraqspicombinedseqxfer

The currxfer field is read by the IRQ handler without holding the lock to check if a transfer is in progress. When clearing currxfer in the combined sequence transfer loop, protect it with the spinlock to prevent a race with the interrupt handler.

Protect the currxfer clearing at the exit path of tegraqspicombinedseqxfer() 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 currxfer value, leading to NULL pointer dereference or use-after-free.

Affected Software

15 affected components
Linux Linux kernel
Linux Linux kernel>=5.15.198<5.15.200
Linux Linux kernel>=6.1.160<6.1.163
Linux Linux kernel>=6.6.120<6.6.124
Linux Linux kernel>=6.12.63<6.12.70
Linux Linux kernel>=6.17.13<6.18
Linux Linux kernel>=6.18.2<6.18.10
Linux Linux kernel=6.19-rc1
Linux Linux kernel=6.19-rc2
Linux Linux kernel=6.19-rc3
Linux Linux kernel=6.19-rc4
Linux Linux kernel=6.19-rc5
Linux Linux kernel=6.19-rc6
Linux Linux kernel=6.19-rc7
Linux Linux kernel=6.19-rc8

Event History

Feb 14, 2026
CVE Published
via MITRE·04:27 PM
Data Sourced
via MITRE·04:27 PM
Description
Data Sourced
via NVD·05:15 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-23202?

CVE-2026-23202 has been rated as medium severity due to potential data corruption risks in the Linux kernel.

2

How do I fix CVE-2026-23202?

To fix CVE-2026-23202, ensure you update your Linux kernel to the patched version that resolves this vulnerability.

3

Which software is affected by CVE-2026-23202?

CVE-2026-23202 affects the Linux kernel, particularly the tegra210-quad spi driver.

4

What impact does CVE-2026-23202 have on systems?

CVE-2026-23202 can lead to data integrity issues due to improper locking of the curr_xfer field during IRQ handling.

5

Is there a workaround for CVE-2026-23202?

While a direct workaround is not specified, upgrading to a secure kernel version is the most effective mitigation for CVE-2026-23202.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203