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

exploitDog

fstec логотип

BDU:2024-07829

Опубликовано: 04 сент. 2023
Источник: fstec
CVSS3: 8.8
CVSS2: 6.8
EPSS Низкий

Описание

Уязвимость компонента sun6i ядра операционной системы Linux связана с конкурентным доступом к ресурсу (состояние гонки). Эксплуатация уязвимости может позволить нарушителю выполнить произвольный код с повышенными привилегиями.

Вендор

Canonical Ltd.
Сообщество свободного программного обеспечения
ООО «Ред Софт»

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

Ubuntu
Debian GNU/Linux
РЕД ОС
Linux

Версия ПО

20.04 LTS (Ubuntu)
11 (Debian GNU/Linux)
12 (Debian GNU/Linux)
7.3 (РЕД ОС)
22.04 LTS (Ubuntu)
от 6.2 до 6.5.5 включительно (Linux)
от 5.16 до 6.1.55 включительно (Linux)
от 4.0 до 5.15.133 включительно (Linux)

Тип ПО

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

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

Canonical Ltd. Ubuntu 20.04 LTS
Сообщество свободного программного обеспечения Debian GNU/Linux 11
Сообщество свободного программного обеспечения Debian GNU/Linux 12
ООО «Ред Софт» РЕД ОС 7.3
Canonical Ltd. Ubuntu 22.04 LTS
Сообщество свободного программного обеспечения Linux до 5.15.134
Сообщество свободного программного обеспечения Linux до 6.1.56
Сообщество свободного программного обеспечения Linux до 6.5.6
Сообщество свободного программного обеспечения Linux до 6.6

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

Средний уровень опасности (базовая оценка CVSS 2.0 составляет 6,8)
Высокий уровень опасности (базовая оценка CVSS 3.0 составляет 8,8)

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

Использование рекомендаций:
Для Linux:
https://lore.kernel.org/linux-cve-announce/2024030252-CVE-2023-52517-30dc@gregkh/T/#u
https://git.kernel.org/linus/1f11f4202caf5710204d334fe63392052783876d
https://git.kernel.org/stable/c/1f11f4202caf5710204d334fe63392052783876d
https://git.kernel.org/stable/c/36b29974a7ad2ff604c24ad348f940506c7b1209
https://git.kernel.org/stable/c/4e149d524678431638ff378ef6025e4e89b71097
https://git.kernel.org/stable/c/bd1ec7f9983b5cd3c77e0f7cda3fa8aed041af2f
https://kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.134
https://kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.56
https://kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.5.6
Для РедоС:
http://repo.red-soft.ru/redos/7.3c/x86_64/updates/
Для Debian GNU/Linux:
https://security-tracker.debian.org/tracker/CVE-2023-52517
Для Ubuntu:
https://ubuntu.com/security/CVE-2023-52517

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

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

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

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

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

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

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

EPSS

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

8.8 High

CVSS3

6.8 Medium

CVSS2

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

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

In the Linux kernel, the following vulnerability has been resolved: spi: sun6i: fix race between DMA RX transfer completion and RX FIFO drain Previously the transfer complete IRQ immediately drained to RX FIFO to read any data remaining in FIFO to the RX buffer. This behaviour is correct when dealing with SPI in interrupt mode. However in DMA mode the transfer complete interrupt still fires as soon as all bytes to be transferred have been stored in the FIFO. At that point data in the FIFO still needs to be picked up by the DMA engine. Thus the drain procedure and DMA engine end up racing to read from RX FIFO, corrupting any data read. Additionally the RX buffer pointer is never adjusted according to DMA progress in DMA mode, thus calling the RX FIFO drain procedure in DMA mode is a bug. Fix corruptions in DMA RX mode by draining RX FIFO only in interrupt mode. Also wait for completion of RX DMA when in DMA mode before returning to ensure all data has been copied to the supplied memo...

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

In the Linux kernel, the following vulnerability has been resolved: spi: sun6i: fix race between DMA RX transfer completion and RX FIFO drain Previously the transfer complete IRQ immediately drained to RX FIFO to read any data remaining in FIFO to the RX buffer. This behaviour is correct when dealing with SPI in interrupt mode. However in DMA mode the transfer complete interrupt still fires as soon as all bytes to be transferred have been stored in the FIFO. At that point data in the FIFO still needs to be picked up by the DMA engine. Thus the drain procedure and DMA engine end up racing to read from RX FIFO, corrupting any data read. Additionally the RX buffer pointer is never adjusted according to DMA progress in DMA mode, thus calling the RX FIFO drain procedure in DMA mode is a bug. Fix corruptions in DMA RX mode by draining RX FIFO only in interrupt mode. Also wait for completion of RX DMA when in DMA mode before returning to ensure all data has been copied to the supplied memo...

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

In the Linux kernel, the following vulnerability has been resolved: spi: sun6i: fix race between DMA RX transfer completion and RX FIFO drain Previously the transfer complete IRQ immediately drained to RX FIFO to read any data remaining in FIFO to the RX buffer. This behaviour is correct when dealing with SPI in interrupt mode. However in DMA mode the transfer complete interrupt still fires as soon as all bytes to be transferred have been stored in the FIFO. At that point data in the FIFO still needs to be picked up by the DMA engine. Thus the drain procedure and DMA engine end up racing to read from RX FIFO, corrupting any data read. Additionally the RX buffer pointer is never adjusted according to DMA progress in DMA mode, thus calling the RX FIFO drain procedure in DMA mode is a bug. Fix corruptions in DMA RX mode by draining RX FIFO only in interrupt mode. Also wait for completion of RX DMA when in DMA mode before returning to ensure all data has been copied to the supplied memor

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

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

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

In the Linux kernel, the following vulnerability has been resolved: spi: sun6i: fix race between DMA RX transfer completion and RX FIFO drain Previously the transfer complete IRQ immediately drained to RX FIFO to read any data remaining in FIFO to the RX buffer. This behaviour is correct when dealing with SPI in interrupt mode. However in DMA mode the transfer complete interrupt still fires as soon as all bytes to be transferred have been stored in the FIFO. At that point data in the FIFO still needs to be picked up by the DMA engine. Thus the drain procedure and DMA engine end up racing to read from RX FIFO, corrupting any data read. Additionally the RX buffer pointer is never adjusted according to DMA progress in DMA mode, thus calling the RX FIFO drain procedure in DMA mode is a bug. Fix corruptions in DMA RX mode by draining RX FIFO only in interrupt mode. Also wait for completion of RX DMA when in DMA mode before returning to ensure all data has been copied to the supplied me...

EPSS

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

8.8 High

CVSS3

6.8 Medium

CVSS2