CVE-2026-31688

✕ Withdrawn — historical dataHIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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:

driver core: enforce device_lock for driver_match_device()

Currently, driver_match_device() is called from three sites. One site (__device_attach_driver) holds device_lock(dev), but the other two (bind_store and __driver_attach) do not. This inconsistency means that bus match() callbacks are not guaranteed to be called with the lock held.

Fix this by introducing driver_match_device_locked(), which guarantees holding the device lock using a scoped guard. Replace the unlocked calls in bind_store() and __driver_attach() with this new helper. Also add a lock assertion to driver_match_device() to enforce this guarantee.

This consistency also fixes a known race condition. The driver_override implementation relies on the device_lock, so the missing lock led to the use-after-free (UAF) reported in Bugzilla for buses using this field.

Stress testing the two newly locked paths for 24 hours with CONFIG_PROVE_LOCKING and CONFIG_LOCKDEP enabled showed no UAF recurrence and no lockdep warnings.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
1.5%
KEV
Not listed

Published

April 27, 2026

Last Modified

May 6, 2026

Advisory Details (1)

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

driver core: enforce device_lock for driver_match_device() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-31688(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 0× in last 7d / 2× 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 102 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-31688?
CVE-2026-31688 is a high vulnerability published on April 27, 2026. In the Linux kernel, the following vulnerability has been resolved: driver core: enforce devicelock for drivermatch_device() Currently, drivermatchdevice() is called from three sites. One site (deviceattachdriver) holds device_lock(dev), but the other two (bindstore and driverattach) do not. This…
When was CVE-2026-31688 disclosed?
CVE-2026-31688 was first published in the National Vulnerability Database on April 27, 2026, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31688 actively exploited?
CVE-2026-31688 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31688?
CVE-2026-31688 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31688?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31688, 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-31688

Explore →

Is Your Infrastructure Affected by CVE-2026-31688?

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

Start Free Scan →Browse All CVEs