CVE-2021-47434

xhci: Fix command ring pointer corruption while aborting a command

MEDIUM
5.5
CVSS Score
Published: May 22, 2024 at 06:19 AM UTC
Updated: June 17, 2026 at 04:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: xhci: Fix command ring pointer corruption while aborting a command The command ring pointer is located at [6:63] bits of the command ring control register (CRCR). All the control bits like command stop, abort are located at [0:3] bits. While aborting a command, we read the CRCR and set the abort bit and write to the CRCR. The read will always give command ring pointer as all zeros. So we essentially write only the control bits. Since we split the 64 bit write into two 32 bit writes, there is a possibility of xHC command ring stopped before the upper dword (all zeros) is written. If that happens, xHC updates the upper dword of its internal command ring pointer with all zeros. Next time, when the command ring is restarted, we see xHC memory access failures. Fix this issue by only writing to the lower dword of CRCR where all control bits are located.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 3.0.49v ≥ 3.2.32v ≥ 3.4.13v ≥ 3.5.6v ≥ 3.6.1v < 4.14.2523.0.49 ≤ v < 3.13.2.32 ≤ v < 3.33.4.13 ≤ v < 3.53.5.6 ≤ v < 3.63.6.1 ≤ v < 3.73.7 ≤ v < 4.14.2523.7 ≤ v < 4.19.2133.7 ≤ v < 5.10.753.7 ≤ v < 5.14.143.7 ≤ v < 5.153.7 ≤ v < 5.4.1554.15 ≤ v < 4.19.2134.20 ≤ v < 5.4.1555.11 ≤ v < 5.14.145.5 ≤ v < 5.10.752818247b6565b7adfbcd53b74509448a8e1fad843.0.493.2.323.4.133.5.63.6.13.75.15 rc15.15 rc25.15 rc35.15 rc45.15 rc588bd928daafb5912c269af628b1e5347620c9a62b92cc66c047ff7cf587b318fe377061a353c120fbc47204b268516ae4085ebdc81a34ddda71b77c4ef6273930e170a4f70a2c7f57a214813c5cf30bbf83994f3e2438b982fb9821d948199b3327638d8
Vendor states this is fixed in 01c2dcb67e71c351006dd17cbba86c26b7f61eaf (fixed)
Vendor states this is fixed in 22bcb65ea41072ab5d03c0c6290e04e0df6d09a0 (fixed)
Vendor states this is fixed in 62c182b5e763e5f4062e72678e72ce3e02dd4d1b (fixed)
Vendor states this is fixed in dec944bb7079b37968cf69c8a438f91f15c4cc61 (fixed)
Vendor states this is fixed in e54abefe703ab7c4e5983e889babd1447738ca42 (fixed)
Vendor states this is fixed in ff0e50d3564f33b7f4b35cadeabd951d66cfc570 (fixed)
Affected range stops below 3.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.6, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 3.7 (unaffected)
Vendor states this is fixed in 4.14.252 (unaffected)
Vendor states this is fixed in 4.19.213 (unaffected)
Vendor states this is fixed in 5.10.75 (unaffected)
Vendor states this is fixed in 5.14.14 (unaffected)
Vendor states this is fixed in 5.15 (unaffected)
Vendor states this is fixed in 5.4.155 (unaffected)

References (6)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/01c2dcb67e71c351006dd17cbba86c26b7f61eaf
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/22bcb65ea41072ab5d03c0c6290e04e0df6d09a0
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/62c182b5e763e5f4062e72678e72ce3e02dd4d1b
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/dec944bb7079b37968cf69c8a438f91f15c4cc61
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e54abefe703ab7c4e5983e889babd1447738ca42
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/ff0e50d3564f33b7f4b35cadeabd951d66cfc570

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card