CVE-2026-31489

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-22. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
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.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

spi: meson-spicc: Fix double-put in remove path

meson_spicc_probe() registers the controller with devm_spi_register_controller(), so teardown already drops the controller reference via devm cleanup.

Calling spi_controller_put() again in meson_spicc_remove() causes a double-put.

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

Published

April 22, 2026

Last Modified

June 19, 2026

Advisory Details (5)

Auto-updated May 17, 2026
No patch confirmed yet.
generic

spi: meson-spicc: Fix double-put in remove path - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: meson-spicc: Fix double-put in remove path - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: meson-spicc: Fix double-put in remove path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/63542bb402b7013171c9f621c28b609eda4dbf1f
generic

spi: meson-spicc: Fix double-put in remove path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/40ad0334c17b23d8b66b1082ad1478a6202e90e2
generic

spi: meson-spicc: Fix double-put in remove path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d645c6d13fa0597935d3d16b09a7ba5d24ed284

Vendor Advisories for CVE-2026-31489(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.259—osv

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.11-1—

Weakness Classification(1)

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

All Vendor Advisories

(23)

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 6× in last 7d / 26× 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 234 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-31489?
CVE-2026-31489 is a high vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: spi: meson-spicc: Fix double-put in remove path mesonspiccprobe() registers the controller with devmspiregister_controller(), so teardown already drops the controller reference via devm cleanup. Calling spicontrollerput() again in…
When was CVE-2026-31489 disclosed?
CVE-2026-31489 was first published in the National Vulnerability Database on April 22, 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-31489 actively exploited?
CVE-2026-31489 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-31489?
CVE-2026-31489 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31489?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31489, 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-31489

Explore →

Is Your Infrastructure Affected by CVE-2026-31489?

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

Start Free Scan →Browse All CVEs