Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 32 days later

    Published

  3. · 8 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-23202, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.10% · top 99% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 88db8bb7ed1bb474618acdf05ebd4f0758d244e2 – < 9fa4262a80f751d14a6a39d2c03f57db68da2618
    • affected 83309dd551cfd60a5a1a98d9cab19f435b44d46d – < 762e2ce71c8f0238e9eaf05d14da803d9a24422f
    • affected c934e40246da2c5726d14e94719c514e30840df8 – < 712cde8d916889e282727cdf304a43683adf899e
    • affected 551060efb156c50fe33799038ba8145418cfdeef – < 6fd446178a610a48e80e5c5b487b0707cd01daac
    • affected 01bbf25c767219b14c3235bfa85906b8d2cb8fbc – < 3bc293d5b56502068481478842f57b3d96e432c7
    • affected b4e002d8a7cee3b1d70efad0e222567f92a73000 – < bf4528ab28e2bf112c3a2cdef44fd13f007781cd
    • affected bb0c58be84f907285af45657c1d4847b960a12bf
    • affected 6.17.13 – < 6.18
  • Linux · Linux

    • affected 5.15.198 – < 5.15.200
    • affected 6.1.160 – < 6.1.163
    • affected 6.6.120 – < 6.6.124
    • affected 6.12.63 – < 6.12.70
    • affected 6.18.2 – < 6.18.10

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-23202 badge
[![CVE-2026-23202](https://cveledger.app/badge/CVE-2026-23202.svg)](https://cveledger.app/cve/CVE-2026-23202)

Record last updated .