CVE-2026-46083

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
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: fix resource leaks on device setup failure

Make sure to call controller cleanup() if spi_setup() fails while registering a device to avoid leaking any resources allocated by setup().

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 24, 2026

Advisory Details (6)

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

spi: fix resource leaks on device setup failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: fix resource leaks on device setup failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: fix resource leaks on device setup failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: fix resource leaks on device setup failure - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: fix resource leaks on device setup failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1e774294b2f944f59e03a04eb438768a4b93c3ce
generic

spi: fix resource leaks on device setup failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/11baa8b24bcb07ae2048f2566a220021d766abe0

Vendor Advisories for CVE-2026-46083(2)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-07-11ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-07-11ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-07-11ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-07-11ubuntu

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.

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 12× in last 7d / 46× 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 112 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-46083?
CVE-2026-46083 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: spi: fix resource leaks on device setup failure Make sure to call controller cleanup() if spi_setup() fails while registering a device to avoid leaking any resources allocated by setup().
When was CVE-2026-46083 disclosed?
CVE-2026-46083 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46083 actively exploited?
CVE-2026-46083 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-46083?
CVE-2026-46083 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46083?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46083, 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

Explore the affected products and dependency analysis for CVE-2026-46083

Explore →

Is Your Infrastructure Affected by CVE-2026-46083?

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

Start Free Scan →Browse All CVEs