spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18, 5.15.200, 6.1.163, 6.6.124, 6.12.70, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 88db8bb7ed1bb474618acdf05ebd4f0758d244e2 · fixed in 9fa4262a80f751d14a6a39d2c03f57db68da2618; From 83309dd551cfd60a5a1a98d9cab19f435b44d46d · fixed in 762e2ce71c8f0238e9eaf05d14da803d9a24422f; From c934e40246da2c5726d14e94719c514e30840df8 · fixed in 712cde8d916889e282727cdf304a43683adf899e; From 551060efb156c50fe33799038ba8145418cfdeef · fixed in 6fd446178a610a48e80e5c5b487b0707cd01daac; From 01bbf25c767219b14c3235bfa85906b8d2cb8fbc · fixed in 3bc293d5b56502068481478842f57b3d96e432c7; From b4e002d8a7cee3b1d70efad0e222567f92a73000 · fixed in bf4528ab28e2bf112c3a2cdef44fd13f007781cd; From 6.17.13 · fixed in 6.18
- Linux Linux
From 5.15.198 · fixed in 5.15.200; From 6.1.160 · fixed in 6.1.163; From 6.6.120 · fixed in 6.6.124; From 6.12.63 · fixed in 6.12.70; From 6.18.2 · fixed in 6.18.10
- KernelLinux
From 5.15.198 · fixed in 5.15.200; From 6.1.160 · fixed in 6.1.163; From 6.6.120 · fixed in 6.6.124; From 6.12.63 · fixed in 6.12.70; From 6.18.2 · fixed in 6.18.10