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

exploitDog

fstec логотип

BDU:2026-03535

Опубликовано: 30 мар. 2022
Источник: fstec
CVSS3: 4.7
CVSS2: 3.8
EPSS Низкий

Описание

Уязвимость функции rxrpc_propose_ACK() модуля net/rxrpc/ar-internal.h поддержки сокетов сеанса RxRPC ядра операционной системы Linux связана с ситуацией гонки. Эксплуатация уязвимости может позволить нарушителю вызвать отказ в обслуживании

Вендор

Canonical Ltd.
Сообщество свободного программного обеспечения
Red Hat Inc.

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

Ubuntu
Debian GNU/Linux
Red Hat Enterprise Linux
Linux

Версия ПО

20.04 LTS (Ubuntu)
11 (Debian GNU/Linux)
22.04 LTS (Ubuntu)
9 (Red Hat Enterprise Linux)
от 5.16 до 5.16.18 включительно (Linux)
от 5.17 до 5.17.1 включительно (Linux)
от 5.11 до 5.15.32 включительно (Linux)
24.04 LTS (Ubuntu)
от 4.15 до 5.10.109 включительно (Linux)

Тип ПО

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

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

Canonical Ltd. Ubuntu 20.04 LTS
Сообщество свободного программного обеспечения Debian GNU/Linux 11
Canonical Ltd. Ubuntu 22.04 LTS
Red Hat Inc. Red Hat Enterprise Linux 9
Сообщество свободного программного обеспечения Linux от 5.16 до 5.16.18 включительно
Сообщество свободного программного обеспечения Linux от 5.17 до 5.17.1 включительно
Сообщество свободного программного обеспечения Linux от 5.11 до 5.15.32 включительно
Canonical Ltd. Ubuntu 24.04 LTS
Сообщество свободного программного обеспечения Linux от 4.15 до 5.10.109 включительно

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

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

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

В условиях отсутствия обновлений безопасности от производителя рекомендуется придерживаться "Рекомендаций по безопасной настройке операционных систем LINUX", изложенных в методическом документе ФСТЭК России, утверждённом 25 декабря 2022 года.
Использование рекомендаций:
Для Linux:
https://git.kernel.org/stable/c/54df5a37f1d951ed27fd47bf9b15a42279582110
https://git.kernel.org/stable/c/5e3c11144e557a9dbf9a2f6abe444689ef9d8aae
https://git.kernel.org/stable/c/051360e51341cd17738d82c15a8226010c7cb7f6
https://git.kernel.org/stable/c/8cbf4ae7a2833767d63114573e5f9a45740cc975
https://lore.kernel.org/linux-cve-announce/2025022608-CVE-2022-49149-a2ed@gregkh/
https://git.kernel.org/linus/4a7f62f91933c8ae5308f9127fd8ea48188b6bc3
https://kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.110
https://kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.33
https://kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.16.19
https://kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.17.2
Для Debian GNU/Linux:
https://security-tracker.debian.org/tracker/CVE-2022-49149
Для программных продуктов Red Hat Inc.:
https://access.redhat.com/security/cve/CVE-2022-49149
Для Ubuntu:
https://ubuntu.com/security/CVE-2022-49149

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

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

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

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

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

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

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

EPSS

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

4.7 Medium

CVSS3

3.8 Low

CVSS2

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

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

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix call timer start racing with call destruction The rxrpc_call struct has a timer used to handle various timed events relating to a call. This timer can get started from the packet input routines that are run in softirq mode with just the RCU read lock held. Unfortunately, because only the RCU read lock is held - and neither ref or other lock is taken - the call can start getting destroyed at the same time a packet comes in addressed to that call. This causes the timer - which was already stopped - to get restarted. Later, the timer dispatch code may then oops if the timer got deallocated first. Fix this by trying to take a ref on the rxrpc_call struct and, if successful, passing that ref along to the timer. If the timer was already running, the ref is discarded. The timer completion routine can then pass the ref along to the call's work item when it queues it. If the timer or work item where already q...

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

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix call timer start racing with call destruction The rxrpc_call struct has a timer used to handle various timed events relating to a call. This timer can get started from the packet input routines that are run in softirq mode with just the RCU read lock held. Unfortunately, because only the RCU read lock is held - and neither ref or other lock is taken - the call can start getting destroyed at the same time a packet comes in addressed to that call. This causes the timer - which was already stopped - to get restarted. Later, the timer dispatch code may then oops if the timer got deallocated first. Fix this by trying to take a ref on the rxrpc_call struct and, if successful, passing that ref along to the timer. If the timer was already running, the ref is discarded. The timer completion routine can then pass the ref along to the call's work item when it queues it. If the timer or work item where already q...

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

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix call timer start racing with call destruction The rxrpc_call struct has a timer used to handle various timed events relating to a call. This timer can get started from the packet input routines that are run in softirq mode with just the RCU read lock held. Unfortunately, because only the RCU read lock is held - and neither ref or other lock is taken - the call can start getting destroyed at the same time a packet comes in addressed to that call. This causes the timer - which was already stopped - to get restarted. Later, the timer dispatch code may then oops if the timer got deallocated first. Fix this by trying to take a ref on the rxrpc_call struct and, if successful, passing that ref along to the timer. If the timer was already running, the ref is discarded. The timer completion routine can then pass the ref along to the call's work item when it queues it. If the timer or work item where already

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

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

CVSS3: 4.7
github
11 месяцев назад

In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix call timer start racing with call destruction The rxrpc_call struct has a timer used to handle various timed events relating to a call. This timer can get started from the packet input routines that are run in softirq mode with just the RCU read lock held. Unfortunately, because only the RCU read lock is held - and neither ref or other lock is taken - the call can start getting destroyed at the same time a packet comes in addressed to that call. This causes the timer - which was already stopped - to get restarted. Later, the timer dispatch code may then oops if the timer got deallocated first. Fix this by trying to take a ref on the rxrpc_call struct and, if successful, passing that ref along to the timer. If the timer was already running, the ref is discarded. The timer completion routine can then pass the ref along to the call's work item when it queues it. If the timer or work item where alrea...

EPSS

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

4.7 Medium

CVSS3

3.8 Low

CVSS2