CVE-2026-46203

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-28. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

spi: cadence-quadspi: fix unclocked access on unbind

Make sure that the controller is runtime resumed before disabling it during driver unbind to avoid an unclocked register access.

This issue was flagged by Sashiko when reviewing a controller deregistration fix.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 19, 2026

Advisory Details (2)

Auto-updated Jun 12, 2026
No patch confirmed yet.
generic

spi: cadence-quadspi: fix unclocked access on unbind - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: cadence-quadspi: fix unclocked access on unbind - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/233db2cb14db8b1935dda52a6affd97276462b82

Vendor Advisories for CVE-2026-46203(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (135 versions)7.0.9-1—

Weakness Classification(1)

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

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 87× 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 231 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46203?
CVE-2026-46203 is a high vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: spi: cadence-quadspi: fix unclocked access on unbind Make sure that the controller is runtime resumed before disabling it during driver unbind to avoid an unclocked register access. This issue was flagged by Sashiko when reviewing…
When was CVE-2026-46203 disclosed?
CVE-2026-46203 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46203 actively exploited?
CVE-2026-46203 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 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-46203?
CVE-2026-46203 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-46203?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46203, 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-46203

Explore →

Is Your Infrastructure Affected by CVE-2026-46203?

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

Start Free Scan →Browse All CVEs