CVE-2026-31527

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.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: platform: 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]

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

Published

April 22, 2026

Last Modified

June 1, 2026

Advisory Details (5)

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

driver core: platform: use generic driver_override infrastructure - kernel/git/stable/linux.git - Linux kernel stable tree

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

driver core: platform: use generic driver_override infrastructure - kernel/git/stable/linux.git - Linux kernel stable tree

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

driver core: platform: use generic driver_override infrastructure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7c02a9bd7d14a89065fcf672b86d8e1d1a41d3b1
generic

driver core: platform: use generic driver_override infrastructure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/492349e5e4a369a8b62781100a3ade470bf1ce6b
generic

driver core: platform: use generic driver_override infrastructure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2b38efc05bf7a8568ec74bfffea0f5cfa62bc01d

Vendor Advisories for CVE-2026-31527(2)

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 8× in last 7d / 39× 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 133 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-31527?
CVE-2026-31527 is a high vulnerability published on April 22, 2026. In the Linux kernel, the following vulnerability has been resolved: driver core: platform: 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…
When was CVE-2026-31527 disclosed?
CVE-2026-31527 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on June 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31527 actively exploited?
CVE-2026-31527 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-31527?
CVE-2026-31527 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-31527?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31527, 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-31527

Explore →

Is Your Infrastructure Affected by CVE-2026-31527?

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

Start Free Scan →Browse All CVEs