Command Ring Pointer Corruption Vulnerability in xhci
Summary
GSD-2021-1001811: xhci: Fix command ring pointer corruption while aborting a command. Affects Kernel versions < 62c182b5e763e5f4062e72678e72ce3e02dd4d1b. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The xhci package is a component of the Linux Kernel that provides support for USB 3.0 and later versions. It includes a host controller driver for eXtensible Host Controller Interface (xHCI) compliant USB controllers. The xHCI driver manages the communication between the USB host controller hardware and the operating system. This vulnerability affects the command ring pointer in the xHCI driver, which is used for managing commands sent to USB devices.
Vulnerability Detail
The command ring pointer corruption vulnerability in the xHCI driver occurs when aborting a command. This can lead to the corruption of the command ring pointer, potentially causing the driver to execute unintended commands or fail to execute valid commands. An attacker with local access to a system with a vulnerable xHCI driver could exploit this vulnerability to execute arbitrary code, escalate privileges, or cause a denial of service. The vulnerability has been fixed in Linux Kernel version v4.19.213 by commit 62c182b5e763e5f4062e72678e72ce3e02dd4d1b.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Conclusion
The command ring pointer corruption vulnerability in the xhci package of the Linux Kernel can be mitigated by updating to version v4.19.213 or later. This update includes a fix for the vulnerability, preventing potential exploitation. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability could allow an attacker with local access to execute arbitrary code, escalate privileges, or cause a denial of service.
No, this vulnerability requires local access to the system.
The vulnerability is present in versions prior to v4.19.213.
There are no known instances of this vulnerability being exploited in the wild.
No, updating to the fixed version of the Linux Kernel is the recommended solution.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
