Skip to content
Fencer Vulns
medium 5.5

CVE-2021-47434 json

xhci: Fix command ring pointer corruption while aborting a command

published 2024-05-22 2 y ago modified 2026-06-17 4 mo ago also EUVD-2021-34439

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 14%
public exploits
0
none known

Summary

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.

Patch / fix

  • Linux Linux 3.1, 3.3, 3.5, 3.6, 3.7, 4.14.252, 4.19.213, 5.4.155, 5.10.75, 5.14.14, 5.15
  • linux Debian 14, Debian 13, Debian 12 5.14.16-1

debian advisories DEBIAN-CVE-2021-47434

  • linux Ubuntu 18.04 LTS 4.15.0-166.174
  • linux Ubuntu 20.04 LTS 5.4.0-92.103
  • linux-aws Ubuntu 18.04 LTS 4.15.0-1118.125
  • linux-aws Ubuntu 20.04 LTS 5.4.0-1061.64
  • linux-gcp Ubuntu 20.04 LTS 5.4.0-1059.63
  • linux-ibm Ubuntu 20.04 LTS 5.4.0-1010.11
  • linux-kvm Ubuntu 18.04 LTS 4.15.0-1105.107
  • linux-kvm Ubuntu 20.04 LTS 5.4.0-1051.53

ubuntu advisories UBUNTU-CVE-2021-47434

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-syms SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-122.222.1
  • kernel-source SLES for SAP 12 SP5, SLES 12 SP5 4.12.14-122.222.1
  • kernel-default SLES for SAP 12 SP5, SLES 12 SP5, SLE Workstation Extension 12 SP5 +2 more 4.12.14-122.222.1
  • kernel-obs-build SLE Software Development Kit 12 SP5 4.12.14-122.222.1
  • kernel-rt SLE Real Time 12 SP5 4.12.14-10.191.1
  • kernel-syms-rt SLE Real Time 12 SP5 4.12.14-10.191.1
  • kernel-rt_debug SLE Real Time 12 SP5 4.12.14-10.191.1
  • kernel-source-rt SLE Real Time 12 SP5 4.12.14-10.191.1

suse advisories SUSE-SU-2024:2561-1SUSE-SU-2024:2381-1SUSE-SU-2024:2360-1SUSE-SU-2024:2190-1SUSE-SU-2024:2189-1SUSE-SU-2024:2185-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-47434 updated cvss 5.1

kernel: xhci: Fix command ring pointer corruption while aborting a command

  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.