Логотип exploitDog
Консоль
Логотип exploitDog

exploitDog

fstec логотип

BDU:2025-14327

Опубликовано: 08 окт. 2021
Источник: fstec
CVSS3: 5.5
CVSS2: 4.6
EPSS Низкий

Описание

Уязвимость функции xhci_handle_stopped_cmd_ring() модуля drivers/usb/host/xhci-ring.c драйвера поддержки устройств шины USB ядра операционной системы Linux связана с разыменованием недоверенного указателя. Эксплуатация уязвимости может позволить нарушителю оказать воздействие на доступность защищаемой информации

Вендор

Сообщество свободного программного обеспечения

Наименование ПО

Linux

Версия ПО

от 4.20 до 5.4.154 включительно (Linux)
от 5.5 до 5.10.74 включительно (Linux)
от 5.11 до 5.14.13 включительно (Linux)
от 4.15 до 4.19.212 включительно (Linux)
от 2.6.12 до 4.14.251 включительно (Linux)

Тип ПО

Операционная система

Операционные системы и аппаратные платформы

Сообщество свободного программного обеспечения Linux от 4.20 до 5.4.154 включительно
Сообщество свободного программного обеспечения Linux от 5.5 до 5.10.74 включительно
Сообщество свободного программного обеспечения Linux от 5.11 до 5.14.13 включительно
Сообщество свободного программного обеспечения Linux от 4.15 до 4.19.212 включительно
Сообщество свободного программного обеспечения Linux от 2.6.12 до 4.14.251 включительно

Уровень опасности уязвимости

Средний уровень опасности (базовая оценка CVSS 2.0 составляет 4,6)
Средний уровень опасности (базовая оценка CVSS 3.1 составляет 5,5)

Возможные меры по устранению уязвимости

В условиях отсутствия обновлений безопасности от производителя рекомендуется придерживаться "Рекомендаций по безопасной настройке операционных систем LINUX", изложенных в методическом документе ФСТЭК России, утверждённом 25 декабря 2022 года.
Использование рекомендаций:
Для Linux:
https://git.kernel.org/stable/c/22bcb65ea41072ab5d03c0c6290e04e0df6d09a0
https://git.kernel.org/stable/c/62c182b5e763e5f4062e72678e72ce3e02dd4d1b
https://git.kernel.org/stable/c/01c2dcb67e71c351006dd17cbba86c26b7f61eaf
https://git.kernel.org/stable/c/dec944bb7079b37968cf69c8a438f91f15c4cc61
https://git.kernel.org/stable/c/e54abefe703ab7c4e5983e889babd1447738ca42
https://lore.kernel.org/linux-cve-announce/2024052237-CVE-2021-47434-2f8e@gregkh/
https://git.kernel.org/linus/ff0e50d3564f33b7f4b35cadeabd951d66cfc570
https://git.linuxtesting.ru/pub/scm/linux/kernel/git/lvc/linux-stable.git/commit/?h=v5.10.176-lvc1&id=dec944bb7079b37968cf69c8a438f91f15c4cc61
https://kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.14.252
https://kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.19.213
https://kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.155
https://kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.75
https://kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.14.14

Статус уязвимости

Подтверждена производителем

Наличие эксплойта

Данные уточняются

Информация об устранении

Уязвимость устранена

Идентификаторы других систем описаний уязвимостей

EPSS

Процентиль: 1%
0.00008
Низкий

5.5 Medium

CVSS3

4.6 Medium

CVSS2

Связанные уязвимости

CVSS3: 5.5
ubuntu
больше 1 года назад

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.

CVSS3: 5.1
redhat
больше 1 года назад

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.

CVSS3: 5.5
nvd
больше 1 года назад

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.

CVSS3: 5.5
debian
больше 1 года назад

In the Linux kernel, the following vulnerability has been resolved: x ...

CVSS3: 5.5
github
больше 1 года назад

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.

EPSS

Процентиль: 1%
0.00008
Низкий

5.5 Medium

CVSS3

4.6 Medium

CVSS2