CVE-2026-23202

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-02-14. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

February 14, 2026

Last Modified

June 17, 2026

Advisory Details (6)

Auto-updated Aug 7, 2026
No patch confirmed yet.
generic

spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bf4528ab28e2bf112c3a2cdef44fd13f007781cd
generic

spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9fa4262a80f751d14a6a39d2c03f57db68da2618
generic

spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/762e2ce71c8f0238e9eaf05d14da803d9a24422f
generic

spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/712cde8d916889e282727cdf304a43683adf899e
generic

spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6fd446178a610a48e80e5c5b487b0707cd01daac
generic

spi: tegra210-quad: Protect curr_xfer in tegra_qspi_combined_seq_xfer - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3bc293d5b56502068481478842f57b3d96e432c7

Patch Availability(9)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.162-1~deb11u1 (15 versions)6.1.164-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (47 versions)6.1.164-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.73-1~bpo12+1 (12 versions)6.12.73-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (99 versions)6.18.10-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(15)

Data Freshness Timeline

(refreshed 4× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 167 total refreshes for this CVE.

  1. 2026-09-18 21:36 UTCOSV refresh
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-08-31 00:23 UTCOSV refresh
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:48 UTCEPSS rescore
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 13:47 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 02:14 UTCEPSS rescore
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 10:01 UTCEG score recompute
  6. 2026-08-14 10:01 UTCVendor advisory
  7. 2026-08-14 10:01 UTCGHSA enrichment
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-13 02:20 UTCEG score recompute
  10. 2026-08-13 02:20 UTCVendor advisory
  11. 2026-08-13 02:20 UTCGHSA enrichment
  12. 2026-08-12 13:50 UTCEPSS rescore
  13. 2026-08-11 07:52 UTCEG score recompute
  14. 2026-08-11 07:52 UTCVendor advisory
  15. 2026-08-11 07:52 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-09 14:35 UTCEG score recompute
  18. 2026-08-09 14:35 UTCVendor advisory
  19. 2026-08-09 14:35 UTCGHSA enrichment
  20. 2026-08-09 13:46 UTCEPSS rescore
  21. 2026-08-08 16:37 UTCEPSS rescore
  22. 2026-08-07 21:54 UTCEG score recompute
  23. 2026-08-07 21:54 UTCVendor advisory
  24. 2026-08-07 21:54 UTCGHSA enrichment
  25. 2026-08-06 13:46 UTCEPSS rescore
  26. 2026-08-06 03:46 UTCEG score recompute
  27. 2026-08-06 03:46 UTCVendor advisory
  28. 2026-08-06 03:46 UTCGHSA enrichment
  29. 2026-08-05 19:17 UTCEPSS rescore
  30. 2026-08-03 10:35 UTCEPSS rescore
  31. 2026-08-02 20:32 UTCEG score recompute
  32. 2026-08-02 20:32 UTCVendor advisory
  33. 2026-08-02 20:32 UTCGHSA enrichment
  34. 2026-08-02 02:26 UTCEPSS rescore
  35. 2026-08-01 04:15 UTCEPSS rescore
  36. 2026-07-30 01:30 UTCEPSS rescore
  37. 2026-07-25 14:17 UTCEPSS rescore
  38. 2026-07-25 14:17 UTCEPSS rescore
  39. 2026-07-24 14:17 UTCEPSS rescore
  40. 2026-07-23 14:18 UTCEPSS rescore
  41. 2026-07-23 14:18 UTCEPSS rescore
  42. 2026-07-23 03:06 UTCEG score recompute
  43. 2026-07-22 14:08 UTCEPSS rescore
  44. 2026-07-21 15:24 UTCEPSS rescore
  45. 2026-07-21 15:24 UTCEPSS rescore
  46. 2026-07-20 17:08 UTCEPSS rescore
  47. 2026-07-19 14:31 UTCEPSS rescore
  48. 2026-07-19 14:31 UTCEPSS rescore
  49. 2026-07-18 10:04 UTCEPSS rescore
  50. 2026-07-18 10:04 UTCEPSS rescore
  51. 2026-07-17 14:29 UTCOSV refresh
  52. 2026-07-16 17:03 UTCEPSS rescore
  53. 2026-07-16 17:03 UTCEPSS rescore
  54. 2026-07-15 16:57 UTCEPSS rescore
  55. 2026-07-15 16:57 UTCEPSS rescore
  56. 2026-07-15 02:00 UTCEPSS rescore
  57. 2026-07-15 02:00 UTCEPSS rescore
  58. 2026-07-13 22:30 UTCEPSS rescore
  59. 2026-07-13 06:13 UTCEPSS rescore
  60. 2026-07-13 06:13 UTCEPSS rescore
  61. 2026-07-11 08:27 UTCEPSS rescore
  62. 2026-07-09 19:10 UTCEPSS rescore
  63. 2026-07-08 15:15 UTCEPSS rescore
  64. 2026-07-08 15:15 UTCEPSS rescore
  65. 2026-07-07 13:46 UTCEPSS rescore
  66. 2026-07-06 16:27 UTCEPSS rescore
  67. 2026-07-06 16:27 UTCEPSS rescore
  68. 2026-07-06 02:23 UTCEPSS rescore
  69. 2026-07-06 02:23 UTCEPSS rescore
  70. 2026-07-05 02:30 UTCEPSS rescore
  71. 2026-07-04 06:31 UTCEPSS rescore
  72. 2026-07-04 06:31 UTCEPSS rescore
  73. 2026-07-01 15:06 UTCEPSS rescore
  74. 2026-07-01 15:06 UTCEPSS rescore
  75. 2026-06-30 23:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-23202?
CVE-2026-23202 is a medium vulnerability published on February 14, 2026. In the Linux kernel, the following vulnerability has been resolved: spi: tegra210-quad: Protect currxfer in tegraqspicombinedseq_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…
When was CVE-2026-23202 disclosed?
CVE-2026-23202 was first published in the National Vulnerability Database on February 14, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23202 actively exploited?
CVE-2026-23202 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.2% of all scored CVEs.
What is the CVSS score of CVE-2026-23202?
CVE-2026-23202 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23202?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23202, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-23202

Explore →

Is Your Infrastructure Affected by CVE-2026-23202?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.