CVE-2026-53051

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

A fix is available — apply it.

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

PCI: tegra194: Fix CBB timeout caused by DBI access before core power-on

When PERST# is deasserted twice (assert -> deassert -> assert -> deassert), a CBB (Control Backbone) timeout occurs at DBI register offset 0x8bc (PCIE_MISC_CONTROL_1_OFF). This happens because pci_epc_deinit_notify() and dw_pcie_ep_cleanup() are called before reset_control_deassert() powers on the controller core.

The call chain that causes the timeout:

pex_ep_event_pex_rst_deassert() pci_epc_deinit_notify() pci_epf_test_epc_deinit() pci_epf_test_clear_bar() pci_epc_clear_bar() dw_pcie_ep_clear_bar() __dw_pcie_ep_reset_bar() dw_pcie_dbi_ro_wr_en() <- Accesses 0x8bc DBI register reset_control_deassert(pcie->core_rst) <- Core powered on HERE

The DBI registers, including PCIE_MISC_CONTROL_1_OFF (0x8bc), are only accessible after the controller core is powered on via reset_control_deassert(pcie->core_rst). Accessing them before this point results in a CBB timeout because the hardware is not yet operational.

Fix this by moving pci_epc_deinit_notify() and dw_pcie_ep_cleanup() to after reset_control_deassert(pcie->core_rst), ensuring the controller is fully powered on before any DBI register accesses occur.

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

Published

June 24, 2026

Last Modified

July 21, 2026

Advisory Details (4)

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

PCI: tegra194: Fix CBB timeout caused by DBI access before core power-on - kernel/git/stable/linux.git - Linux kernel stable tree

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

PCI: tegra194: Fix CBB timeout caused by DBI access before core power-on - kernel/git/stable/linux.git - Linux kernel stable tree

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

PCI: tegra194: Fix CBB timeout caused by DBI access before core power-on - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/34b3eef48d980cd37b876e128bbf314f69fb5d70
generic

PCI: tegra194: Fix CBB timeout caused by DBI access before core power-on - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/010983063a806720b45778d191335f8ea864fea3

Vendor Advisories for CVE-2026-53051(1)

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

(2 across 2 ecosystems)
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

All Vendor Advisories

(8)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-53051?
CVE-2026-53051 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: PCI: tegra194: Fix CBB timeout caused by DBI access before core power-on When PERST# is deasserted twice (assert -> deassert -> assert -> deassert), a CBB (Control Backbone) timeout occurs at DBI register offset 0x8bc…
When was CVE-2026-53051 disclosed?
CVE-2026-53051 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53051 actively exploited?
CVE-2026-53051 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.3% of all scored CVEs.
What is the CVSS score of CVE-2026-53051?
CVE-2026-53051 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53051?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53051, 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-53051

Explore →

Is Your Infrastructure Affected by CVE-2026-53051?

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