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-23207spi: tegra210-quad: Protect curr_xfer check in IRQ handler

Description

In the Linux kernel, the following vulnerability has been resolved: spi: tegra210-quad: Protect curr_xfer check in IRQ handler Now that all other accesses to curr_xfer are done under the lock, protect the curr_xfer NULL check in tegra_qspi_isr_thread() with the spinlock. Without this protection, the following race can occur: CPU0 (ISR thread) CPU1 (timeout path) ---------------- ------------------- if (!tqspi->curr_xfer) // sees non-NULL spin_lock() tqspi->curr_xfer = NULL spin_unlock() handle_*_xfer() spin_lock() t = tqspi->curr_xfer // NULL! ... t->len ... // NULL dereference! With this patch, all curr_xfer accesses are now properly synchronized. Although all accesses to curr_xfer are done under the lock, in tegra_qspi_isr_thread() it checks for NULL, releases the lock and reacquires it later in handle_cpu_based_xfer()/handle_dma_based_xfer(). There is a potential for an update in between, which could cause a NULL pointer dereference. To handle this, add a NULL check inside the handlers after acquiring the lock. This ensures that if the timeout path has already cleared curr_xfer, the handler will safely return without dereferencing the NULL pointer.

Timeline

  1. ID reserved

    By Linux

  2. · 32 days later

    Published

  3. · 9 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-23207, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (19 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 4.7.

Affected products

  • Linux · Linux

    • affected 83309dd551cfd60a5a1a98d9cab19f435b44d46d – < 8261fa3da6e9001be95a54b857df9759e9098d2f
    • affected c934e40246da2c5726d14e94719c514e30840df8 – < 513587caec66b67243027f26867ad3512f06744f
    • affected 551060efb156c50fe33799038ba8145418cfdeef – < 84e926c1c272a35ddb9b86842d32fa833a60dfc7
    • affected 01bbf25c767219b14c3235bfa85906b8d2cb8fbc – < 2ac3a105e51496147c0e44e49466eecfcc532d57
    • affected b4e002d8a7cee3b1d70efad0e222567f92a73000 – < edf9088b6e1d6d88982db7eb5e736a0e4fbcc09e
    • affected 88db8bb7ed1bb474618acdf05ebd4f0758d244e2
    • affected bb0c58be84f907285af45657c1d4847b960a12bf
    • affected 5.15.198 – < 5.16
    • affected 6.17.13 – < 6.18
  • Linux · Linux

    • affected 6.1.160 – < 6.1.191
    • affected 6.6.120 – < 6.6.160
    • affected 6.12.63 – < 6.12.80
    • affected 6.18.2 – < 6.18.10

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .