CVE-2026-53051PCI: tegra194: Fix CBB timeout caused by DBI access before core power-on
- 5.5MediumCVSS base score
- 0.16%Exploitation in 30 daysEPSS · top 95% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 15 days later
· 15 days later
Published
- 5 months later
· 5 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.16% · top 95% of all CVEs (20 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 72034050ccf4202cd6558b0afd2474f756ea3b9b – < 010983063a806720b45778d191335f8ea864fea3
- affected 40e2125381dc11379112485e3eefdd25c6df5375 – < b059a41bdd5b202b2b9d7708403fb43c69689e53
- affected 40e2125381dc11379112485e3eefdd25c6df5375 – < ce899f9c019591b73ef84b9afa332ed53beece25
- affected 40e2125381dc11379112485e3eefdd25c6df5375 – < 34b3eef48d980cd37b876e128bbf314f69fb5d70
- affected 70212c2300971506e986d95000d2745529cac9d7
- affected 6.12.2 – < 6.12.91
- affected 6.11.11 – < 6.12
- affected 6.13
- unaffected < 6.13
- unaffected 6.12.91 – ≤ 6.12.*
- unaffected 6.18.33 – ≤ 6.18.*
- unaffected 7.0.10 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References4
- https://git.kernel.org/stable/c/010983063a806720b45778d191335f8ea864fea3 (opens in a new tab)
- https://git.kernel.org/stable/c/b059a41bdd5b202b2b9d7708403fb43c69689e53 (opens in a new tab)
- https://git.kernel.org/stable/c/ce899f9c019591b73ef84b9afa332ed53beece25 (opens in a new tab)
- https://git.kernel.org/stable/c/34b3eef48d980cd37b876e128bbf314f69fb5d70 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-38919 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-53051)Record last updated .