Service interruption via pre-power-on DBI access
Published Jun 24, 2026 · Updated Jun 24, 2026
Improper hardware state handling in the Linux Kernel allows local users to trigger a Control Backbone timeout through repeated PERST# transitions. The Tegra194 PCIe endpoint reset path calls pci_epc_deinit_notify() and dw_pcie_ep_cleanup() before reset_control_deassert() powers the controller core, causing DBI register offset 0x8bc to be read while the hardware is unavailable. Triggering requires the Tegra194 endpoint controller and a second assert-deassert cycle; the resulting timeout interrupts availability without reported data disclosure or modification.
Summary
What happened
Improper hardware state handling in the Linux Kernel allows local users to trigger a Control Backbone timeout through repeated PERST# transitions. The Tegra194 PCIe endpoint reset path calls pci_epc_deinit_notify() and dw_pcie_ep_cleanup() before reset_control_deassert() powers the controller core, causing DBI register offset 0x8bc to be read while the hardware is unavailable. Triggering requires the Tegra194 endpoint controller and a second assert-deassert cycle; the resulting timeout interrupts availability without reported data disclosure or modification.
The record
- CVE
- CVE-2026-53051
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=40e2125381dc11379112485e3eefdd25c6df5375 <34b3eef48d980cd37b876e128bbf314f69fb5d70
- Affected versionversion=40e2125381dc11379112485e3eefdd25c6df5375 <b059a41bdd5b202b2b9d7708403fb43c69689e53
- Affected versionversion=40e2125381dc11379112485e3eefdd25c6df5375 <ce899f9c019591b73ef84b9afa332ed53beece25
- Affected versionversion=6.11.11 <6.12
- Affected versionversion=6.12.2 <6.12.91
- Affected versionversion=6.13
- Affected versionversion=70212c2300971506e986d95000d2745529cac9d7
- Affected versionversion=72034050ccf4202cd6558b0afd2474f756ea3b9b <010983063a806720b45778d191335f8ea864fea3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo