| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2026021437-CVE-2026-23202-0480@gregkh> Date: Sat, 14 Feb 2026 17:28:59 +0100 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2026-23202: spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== 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. The Linux kernel CVE team has assigned CVE-2026-23202 to this issue. Affected and fixed versions =========================== Issue introduced in 5.15.198 with commit 88db8bb7ed1bb474618acdf05ebd4f0758d244e2 and fixed in 5.15.200 with commit 9fa4262a80f751d14a6a39d2c03f57db68da2618 Issue introduced in 6.1.160 with commit 83309dd551cfd60a5a1a98d9cab19f435b44d46d and fixed in 6.1.163 with commit 762e2ce71c8f0238e9eaf05d14da803d9a24422f Issue introduced in 6.6.120 with commit c934e40246da2c5726d14e94719c514e30840df8 and fixed in 6.6.124 with commit 712cde8d916889e282727cdf304a43683adf899e Issue introduced in 6.12.63 with commit 551060efb156c50fe33799038ba8145418cfdeef and fixed in 6.12.70 with commit 6fd446178a610a48e80e5c5b487b0707cd01daac Issue introduced in 6.18.2 with commit 01bbf25c767219b14c3235bfa85906b8d2cb8fbc and fixed in 6.18.10 with commit 3bc293d5b56502068481478842f57b3d96e432c7 Issue introduced in 6.17.13 with commit bb0c58be84f907285af45657c1d4847b960a12bf Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2026-23202 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: drivers/spi/spi-tegra210-quad.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/9fa4262a80f751d14a6a39d2c03f57db68da2618 https://git.kernel.org/stable/c/762e2ce71c8f0238e9eaf05d14da803d9a24422f https://git.kernel.org/stable/c/712cde8d916889e282727cdf304a43683adf899e https://git.kernel.org/stable/c/6fd446178a610a48e80e5c5b487b0707cd01daac https://git.kernel.org/stable/c/3bc293d5b56502068481478842f57b3d96e432c7 https://git.kernel.org/stable/c/bf4528ab28e2bf112c3a2cdef44fd13f007781cd
Powered by blists - more mailing lists