CVE-2026-53120

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-24. 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

A fix is available — apply it.

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

PCI: 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)
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
2%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 23, 2026

Advisory Details (4)

Auto-updated Jul 23, 2026
No patch confirmed yet.
generic

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

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

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

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

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

https://git.kernel.org/stable/c/58a42be0d70307d765594fc581f5f5e5ef059712
generic

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

https://git.kernel.org/stable/c/10a4206a24013be4d558d476010cbf2eb4c9fa64

Vendor Advisories for CVE-2026-53120(2)

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

Patch Availability(8)

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.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1

Weakness Classification(1)

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

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 5× in last 7d / 84× 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 225 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53120?
CVE-2026-53120 is a high vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: PCI: 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-53120 disclosed?
CVE-2026-53120 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53120 actively exploited?
CVE-2026-53120 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.9% of all scored CVEs.
What is the CVSS score of CVE-2026-53120?
CVE-2026-53120 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-53120?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53120, 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-53120

Explore →

Is Your Infrastructure Affected by CVE-2026-53120?

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