Kernel panic via invalid xHCI endpoint dereference
Published Aug 21, 2024 · Updated May 11, 2026
NULL pointer dereference in the xHCI USB host driver in affected Linux kernel branches allows local users to trigger a kernel panic. The xhci_hc_died path directly indexes an endpoint and dereferences it while killing queued URBs after the host controller stops responding, without first verifying that the endpoint exists. The condition requires local low-privileged access and an unresponsive xHCI host controller; the reported consequence is a system crash.
Summary
What happened
NULL pointer dereference in the xHCI USB host driver in affected Linux kernel branches allows local users to trigger a kernel panic. The xhci_hc_died path directly indexes an endpoint and dereferences it while killing queued URBs after the host controller stops responding, without first verifying that the endpoint exists. The condition requires local low-privileged access and an unresponsive xHCI host controller; the reported consequence is a system crash.
The record
- CVE
- CVE-2023-52901
- Published
- Aug 21, 2024
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 21, 2024CVE publishedPublication date reported by the CVE source.
- May 11, 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=3.15
- Affected versionversion=50e8725e7c429701e530439013f9681e1fa36b5d <08864dc14a6803f0377ca77b9740b26db30c020f
- Affected versionversion=50e8725e7c429701e530439013f9681e1fa36b5d <2d2820d5f375563690c96e60676855205abfb7f5
- Affected versionversion=50e8725e7c429701e530439013f9681e1fa36b5d <375be2dd61a072f7b1cac9b17eea59e07b58db3a
- Affected versionversion=50e8725e7c429701e530439013f9681e1fa36b5d <66fc1600855c05c4ba4e997184c91cf298e0405c
- Affected versionversion=50e8725e7c429701e530439013f9681e1fa36b5d <9891e5c73cab3fd9ed532dc50e9799e55e974766
- Affected versionversion=50e8725e7c429701e530439013f9681e1fa36b5d <e8fb5bc76eb86437ab87002d4a36d6da02165654
- Affected versionversion=50e8725e7c429701e530439013f9681e1fa36b5d <f39c813af0b64f44af94e435c07bfa1ddc2575f5
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