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

exploitDog

fstec логотип

BDU:2025-09605

Опубликовано: 30 мая 2025
Источник: fstec
CVSS3: 7
CVSS2: 6
EPSS Низкий

Описание

Уязвимость модуля net/ipv4/udp_offload.c ядра операционной системы Linux связана с некорректным преобразованием типов данных. Эксплуатация уязвимости может позволить нарушителю вызвать отказ в обслуживании

Вендор

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

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

Red Hat Enterprise Linux
Linux

Версия ПО

9 (Red Hat Enterprise Linux)
6.10.14 (Linux)
10 (Red Hat Enterprise Linux)
до 6.16 rc1 (Linux)
от 6.15 до 6.15.3 (Linux)
от 6.12 до 6.12.34 (Linux)
от 6.1.113 до 6.1.142 (Linux)
от 6.6.55 до 6.6.94 (Linux)
6.11.3 (Linux)

Тип ПО

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

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

Red Hat Inc. Red Hat Enterprise Linux 9
Сообщество свободного программного обеспечения Linux 6.10.14
Red Hat Inc. Red Hat Enterprise Linux 10
Сообщество свободного программного обеспечения Linux до 6.16 rc1
Сообщество свободного программного обеспечения Linux от 6.15 до 6.15.3
Сообщество свободного программного обеспечения Linux от 6.12 до 6.12.34
Сообщество свободного программного обеспечения Linux от 6.1.113 до 6.1.142
Сообщество свободного программного обеспечения Linux от 6.6.55 до 6.6.94
Сообщество свободного программного обеспечения Linux 6.11.3

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

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

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

В условиях отсутствия обновлений безопасности от производителя рекомендуется придерживаться "Рекомендаций по безопасной настройке операционных систем LINUX", изложенных в методическом документе ФСТЭК России, утверждённом 25 декабря 2022 года.
Использование рекомендаций:
Для Linux:
https://lore.kernel.org/linux-cve-announce/2025070328-CVE-2025-38124-bc19@gregkh/
https://git.kernel.org/stable/c/0e65f38bd1aa14ea86e221b7bb814d38278d86c3
https://git.kernel.org/stable/c/3382a1ed7f778db841063f5d7e317ac55f9e7f72
https://git.kernel.org/stable/c/4399f59a9467a324ed46657555f0e1f209a14acb
https://git.kernel.org/stable/c/85eef1748c024da1a191aed56b30a3a65958c50c
https://git.kernel.org/stable/c/a04302867094bdc6efac1b598370fc47cf3f2388
Для программных продуктов Red Hat Inc.:
https://access.redhat.com/security/cve/CVE-2025-38124

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

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

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

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

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

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

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

EPSS

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

7 High

CVSS3

6 Medium

CVSS2

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

ubuntu
около 2 месяцев назад

In the Linux kernel, the following vulnerability has been resolved: net: fix udp gso skb_segment after pull from frag_list Commit a1e40ac5b5e9 ("net: gso: fix udp gso fraglist segmentation after pull from frag_list") detected invalid geometry in frag_list skbs and redirects them from skb_segment_list to more robust skb_segment. But some packets with modified geometry can also hit bugs in that code. We don't know how many such cases exist. Addressing each one by one also requires touching the complex skb_segment code, which risks introducing bugs for other types of skbs. Instead, linearize all these packets that fail the basic invariants on gso fraglist skbs. That is more robust. If only part of the fraglist payload is pulled into head_skb, it will always cause exception when splitting skbs by skb_segment. For detailed call stack information, see below. Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or...

CVSS3: 7
redhat
около 2 месяцев назад

In the Linux kernel, the following vulnerability has been resolved: net: fix udp gso skb_segment after pull from frag_list Commit a1e40ac5b5e9 ("net: gso: fix udp gso fraglist segmentation after pull from frag_list") detected invalid geometry in frag_list skbs and redirects them from skb_segment_list to more robust skb_segment. But some packets with modified geometry can also hit bugs in that code. We don't know how many such cases exist. Addressing each one by one also requires touching the complex skb_segment code, which risks introducing bugs for other types of skbs. Instead, linearize all these packets that fail the basic invariants on gso fraglist skbs. That is more robust. If only part of the fraglist payload is pulled into head_skb, it will always cause exception when splitting skbs by skb_segment. For detailed call stack information, see below. Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one or...

nvd
около 2 месяцев назад

In the Linux kernel, the following vulnerability has been resolved: net: fix udp gso skb_segment after pull from frag_list Commit a1e40ac5b5e9 ("net: gso: fix udp gso fraglist segmentation after pull from frag_list") detected invalid geometry in frag_list skbs and redirects them from skb_segment_list to more robust skb_segment. But some packets with modified geometry can also hit bugs in that code. We don't know how many such cases exist. Addressing each one by one also requires touching the complex skb_segment code, which risks introducing bugs for other types of skbs. Instead, linearize all these packets that fail the basic invariants on gso fraglist skbs. That is more robust. If only part of the fraglist payload is pulled into head_skb, it will always cause exception when splitting skbs by skb_segment. For detailed call stack information, see below. Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - one o

debian
около 2 месяцев назад

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

github
около 2 месяцев назад

In the Linux kernel, the following vulnerability has been resolved: net: fix udp gso skb_segment after pull from frag_list Commit a1e40ac5b5e9 ("net: gso: fix udp gso fraglist segmentation after pull from frag_list") detected invalid geometry in frag_list skbs and redirects them from skb_segment_list to more robust skb_segment. But some packets with modified geometry can also hit bugs in that code. We don't know how many such cases exist. Addressing each one by one also requires touching the complex skb_segment code, which risks introducing bugs for other types of skbs. Instead, linearize all these packets that fail the basic invariants on gso fraglist skbs. That is more robust. If only part of the fraglist payload is pulled into head_skb, it will always cause exception when splitting skbs by skb_segment. For detailed call stack information, see below. Valid SKB_GSO_FRAGLIST skbs - consist of two or more segments - the head_skb holds the protocol headers plus first gso_size - on...

EPSS

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

7 High

CVSS3

6 Medium

CVSS2