CVE-2026-31487

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-04-22. 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

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: use generic driver_override infrastructure

When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF.

Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally.

Note that calling match() from __driver_attach() without the device lock held is intentional. [1]

Also note that we do not enable the driver_override feature of struct bus_type, as SPI - in contrast to most other buses - passes "" to sysfs_emit() when the driver_override pointer is NULL. Thus, printing "\n" instead of "(null)\n".

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
1%
KEV
Not listed

Published

April 22, 2026

Last Modified

April 28, 2026

Advisory Details (4)

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

spi: use generic driver_override infrastructure - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: use generic driver_override infrastructure - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: use generic driver_override infrastructure - kernel/git/stable/linux.git - Linux kernel stable tree

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

spi: use generic driver_override infrastructure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c73a58661a760373d08a6883af4f0bb5cc991a67

Vendor Advisories for CVE-2026-31487(1)

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 @ 6.12.80—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)——
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

(13)

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 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 184 total refreshes for this CVE.

  1. 2026-09-12 15:01 UTCEPSS rescore
  2. 2026-09-11 14:52 UTCEPSS rescore
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-08 22:00 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-06 13:47 UTCEPSS rescore
  7. 2026-09-04 05:06 UTCEPSS rescore
  8. 2026-09-02 14:11 UTCEPSS rescore
  9. 2026-09-02 03:04 UTCOSV refresh
  10. 2026-09-01 13:53 UTCEPSS rescore
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-27 14:25 UTCEPSS rescore
  13. 2026-08-26 14:46 UTCEPSS rescore
  14. 2026-08-24 14:17 UTCEPSS rescore
  15. 2026-08-23 00:19 UTCEPSS rescore
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-19 17:03 UTCEPSS rescore
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-16 06:00 UTCEG score recompute
  22. 2026-08-16 06:00 UTCVendor advisory
  23. 2026-08-16 06:00 UTCGHSA enrichment
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 75 more
  1. 2026-08-14 04:19 UTCVendor advisory
  2. 2026-08-14 04:19 UTCGHSA enrichment
  3. 2026-08-12 23:31 UTCVendor advisory
  4. 2026-08-12 23:31 UTCGHSA enrichment
  5. 2026-08-12 00:56 UTCVendor advisory
  6. 2026-08-12 00:56 UTCGHSA enrichment
  7. 2026-08-11 02:21 UTCEG score recompute
  8. 2026-08-11 02:21 UTCVendor advisory
  9. 2026-08-11 02:21 UTCGHSA enrichment
  10. 2026-08-11 00:00 UTCEPSS rescore
  11. 2026-08-10 02:09 UTCVendor advisory
  12. 2026-08-10 02:09 UTCGHSA enrichment
  13. 2026-08-09 03:33 UTCEG score recompute
  14. 2026-08-09 03:33 UTCVendor advisory
  15. 2026-08-09 03:33 UTCGHSA enrichment
  16. 2026-08-08 16:37 UTCEPSS rescore
  17. 2026-08-07 20:23 UTCEG score recompute
  18. 2026-08-07 20:23 UTCVendor advisory
  19. 2026-08-07 20:23 UTCGHSA enrichment
  20. 2026-08-06 21:48 UTCEG score recompute
  21. 2026-08-06 21:48 UTCVendor advisory
  22. 2026-08-06 21:48 UTCGHSA enrichment
  23. 2026-08-06 13:46 UTCEPSS rescore
  24. 2026-08-05 23:05 UTCEG score recompute
  25. 2026-08-05 23:05 UTCVendor advisory
  26. 2026-08-05 23:05 UTCGHSA enrichment
  27. 2026-08-05 19:17 UTCEPSS rescore
  28. 2026-08-04 15:10 UTCEPSS rescore
  29. 2026-08-04 10:38 UTCEPSS rescore
  30. 2026-08-03 21:14 UTCVendor advisory
  31. 2026-08-03 21:14 UTCGHSA enrichment
  32. 2026-08-02 12:28 UTCEG score recompute
  33. 2026-08-02 12:28 UTCVendor advisory
  34. 2026-08-02 12:28 UTCGHSA enrichment
  35. 2026-08-02 02:27 UTCEPSS rescore
  36. 2026-08-01 04:16 UTCEPSS rescore
  37. 2026-07-30 16:27 UTCEPSS rescore
  38. 2026-07-30 01:30 UTCEPSS rescore
  39. 2026-07-28 15:36 UTCEPSS rescore
  40. 2026-07-26 14:54 UTCEPSS rescore
  41. 2026-07-26 14:54 UTCEPSS rescore
  42. 2026-07-25 14:18 UTCEPSS rescore
  43. 2026-07-25 14:17 UTCEPSS rescore
  44. 2026-07-24 14:17 UTCEPSS rescore
  45. 2026-07-23 03:08 UTCEG score recompute
  46. 2026-07-22 14:08 UTCEPSS rescore
  47. 2026-07-22 14:08 UTCEPSS rescore
  48. 2026-07-21 15:24 UTCEPSS rescore
  49. 2026-07-21 15:24 UTCEPSS rescore
  50. 2026-07-20 17:08 UTCEPSS rescore
  51. 2026-07-20 17:08 UTCEPSS rescore
  52. 2026-07-19 23:48 UTCOSV refresh
  53. 2026-07-19 14:31 UTCEPSS rescore
  54. 2026-07-19 14:31 UTCEPSS rescore
  55. 2026-07-18 10:04 UTCEPSS rescore
  56. 2026-07-18 10:04 UTCEPSS rescore
  57. 2026-07-16 17:03 UTCEPSS rescore
  58. 2026-07-16 17:03 UTCEPSS rescore
  59. 2026-07-15 16:57 UTCEPSS rescore
  60. 2026-07-15 16:57 UTCEPSS rescore
  61. 2026-07-13 22:30 UTCEPSS rescore
  62. 2026-07-13 06:13 UTCEPSS rescore
  63. 2026-07-13 06:13 UTCEPSS rescore
  64. 2026-07-12 05:46 UTCEPSS rescore
  65. 2026-07-11 08:27 UTCEPSS rescore
  66. 2026-07-09 19:10 UTCEPSS rescore
  67. 2026-07-07 13:46 UTCEPSS rescore
  68. 2026-07-06 16:27 UTCEPSS rescore
  69. 2026-07-06 16:27 UTCEPSS rescore
  70. 2026-07-06 02:23 UTCEPSS rescore
  71. 2026-07-06 02:23 UTCEPSS rescore
  72. 2026-07-05 02:30 UTCEPSS rescore
  73. 2026-07-04 06:31 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-31487?
CVE-2026-31487 is a medium vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: spi: use generic driver_override infrastructure When a driver is probed through driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can…
When was CVE-2026-31487 disclosed?
CVE-2026-31487 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on April 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31487 actively exploited?
CVE-2026-31487 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 99.3% of all scored CVEs.
What is the CVSS score of CVE-2026-31487?
CVE-2026-31487 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-31487?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31487, 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-31487

Explore →

Is Your Infrastructure Affected by CVE-2026-31487?

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

Start Free Scan →Browse All CVEs