Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2021-47434

xhci: Fix command ring pointer corruption while aborting a command

Medium5.5EPSS 0.24%
Published
Updated
Reserved
Assigned by
Linux

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.

Scores

CVSS scores of CVE-2021-47434, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (6 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected b92cc66c047ff7cf587b318fe377061a353c120f – < 22bcb65ea41072ab5d03c0c6290e04e0df6d09a0
    • affected b92cc66c047ff7cf587b318fe377061a353c120f – < 62c182b5e763e5f4062e72678e72ce3e02dd4d1b
    • affected b92cc66c047ff7cf587b318fe377061a353c120f – < 01c2dcb67e71c351006dd17cbba86c26b7f61eaf
    • affected b92cc66c047ff7cf587b318fe377061a353c120f – < dec944bb7079b37968cf69c8a438f91f15c4cc61
    • affected b92cc66c047ff7cf587b318fe377061a353c120f – < e54abefe703ab7c4e5983e889babd1447738ca42
    • affected b92cc66c047ff7cf587b318fe377061a353c120f – < ff0e50d3564f33b7f4b35cadeabd951d66cfc570
    • affected bc47204b268516ae4085ebdc81a34ddda71b77c4
    • affected 88bd928daafb5912c269af628b1e5347620c9a62
    • affected 2818247b6565b7adfbcd53b74509448a8e1fad84
    • affected ef6273930e170a4f70a2c7f57a214813c5cf30bb
    • affected f83994f3e2438b982fb9821d948199b3327638d8
    • affected 3.0.49 – < 3.1
    • affected 3.2.32 – < 3.3
    • affected 3.4.13 – < 3.5
    • affected 3.5.6 – < 3.6
    • affected 3.6.1 – < 3.7
  • Linux · Linux

    • affected 3.7
    • unaffected < 3.7
    • unaffected 4.14.252 – ≤ 4.14.*
    • unaffected 4.19.213 – ≤ 4.19.*
    • unaffected 5.4.155 – ≤ 5.4.*
    • unaffected 5.10.75 – ≤ 5.10.*
    • unaffected 5.14.14 – ≤ 5.14.*
    • unaffected 5.15 – ≤ *

References (6)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2021-47434 badge
[![CVE-2021-47434](https://trackcve.app/badge/CVE-2021-47434.svg)](https://trackcve.app/cve/CVE-2021-47434)

Record last updated .