CVE-2022-49962: xhci: Fix null pointer dereference in remove if xHC has only one roothub
In the Linux kernel, the following vulnerability has been resolved:
xhci: Fix null pointer dereference in remove if xHC has only one roothub
The remove path in xhci platform driver tries to remove and put both main
and shared hcds even if only a main hcd exists (one roothub)
This causes a null pointer dereference in reboot for those controllers.
Check that the shared_hcd exists before trying to remove it.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash affected systems during reboot when a specific xHCI USB controller configuration has only one root hub. The public sources describe a null pointer dereference in the controller removal path. No CVSS score or active exploitation evidence is provided.
Executive priority
Treat as a reliability and availability risk until vendor guidance confirms exposure. Prioritize operationally critical Linux systems, appliances, and embedded platforms where reboot failures could affect service restoration or maintenance windows.
Technical view
The xHCI platform driver remove path attempted to remove and release both main and shared HCD objects even when shared_hcd did not exist. For one-roothub xHC controllers, that missing null check could trigger a null pointer dereference during reboot. The fix checks shared_hcd before removal.
Likely exposure
Exposure appears limited to Linux kernels and xHCI platform controllers matching the one-roothub condition. The source bundle lists Linux kernel versions including 5.19, 5.19.8, and 6.0, plus a kernel commit identifier, but distro-specific affected ranges are not established here.
Exploitation context
The CVE is not listed as KEV in the provided data. The sources describe a reboot-time crash condition, not remote code execution, privilege escalation, or confirmed exploitation. Practical exploitability and attack prerequisites are not detailed in the bundle.
Researcher notes
Evidence is narrow: the bundle provides the kernel description and two stable commit references, but no CVSS, CWE, exploit report, or distribution advisory. Avoid broad claims beyond Linux xHCI platform-driver reboot behavior and the shared_hcd null-check fix.
Mitigation direction
Review upstream Linux stable fixes referenced for this CVE.
Map running kernels to vendor advisories and patched distro builds.
Prioritize systems with xHCI platform controllers and reboot reliability requirements.
Use vendor-supported kernel updates rather than ad hoc patching.
Monitor Linux and distribution guidance for clarified affected ranges.
Validation and detection
Inventory Linux kernel versions across servers and embedded devices.
Identify systems using xHCI platform drivers or affected hardware configurations.
Check whether vendor kernels include the referenced stable commits.
Review reboot crash logs for xHCI remove-path null dereference indicators.
Confirm remediation through vendor package or kernel build metadata.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-49962 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:00 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.