Количество 7
Количество 7
CVE-2025-39965
In the Linux kernel, the following vulnerability has been resolved: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI x->id.spi == 0 means "no SPI assigned", but since commit 94f39804d891 ("xfrm: Duplicate SPI Handling"), we now create states and add them to the byspi list with this value. __xfrm_state_delete doesn't remove those states from the byspi list, since they shouldn't be there, and this shows up as a UAF the next time we go through the byspi list.
CVE-2025-39965
In the Linux kernel, the following vulnerability has been resolved: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI x->id.spi == 0 means "no SPI assigned", but since commit 94f39804d891 ("xfrm: Duplicate SPI Handling"), we now create states and add them to the byspi list with this value. __xfrm_state_delete doesn't remove those states from the byspi list, since they shouldn't be there, and this shows up as a UAF the next time we go through the byspi list.
CVE-2025-39965
xfrm: xfrm_alloc_spi shouldn't use 0 as SPI
CVE-2025-39965
In the Linux kernel, the following vulnerability has been resolved: x ...
GHSA-jc8g-4mch-vjcv
In the Linux kernel, the following vulnerability has been resolved: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI x->id.spi == 0 means "no SPI assigned", but since commit 94f39804d891 ("xfrm: Duplicate SPI Handling"), we now create states and add them to the byspi list with this value. __xfrm_state_delete doesn't remove those states from the byspi list, since they shouldn't be there, and this shows up as a UAF the next time we go through the byspi list.
BDU:2025-13242
Уязвимость функции xfrm_alloc_spi() модуля net/xfrm/xfrm_state.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
ELSA-2025-20719
ELSA-2025-20719: Unbreakable Enterprise kernel security update (IMPORTANT)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | CVE-2025-39965 In the Linux kernel, the following vulnerability has been resolved: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI x->id.spi == 0 means "no SPI assigned", but since commit 94f39804d891 ("xfrm: Duplicate SPI Handling"), we now create states and add them to the byspi list with this value. __xfrm_state_delete doesn't remove those states from the byspi list, since they shouldn't be there, and this shows up as a UAF the next time we go through the byspi list. | 0% Низкий | 23 дня назад | |
 | CVE-2025-39965 In the Linux kernel, the following vulnerability has been resolved: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI x->id.spi == 0 means "no SPI assigned", but since commit 94f39804d891 ("xfrm: Duplicate SPI Handling"), we now create states and add them to the byspi list with this value. __xfrm_state_delete doesn't remove those states from the byspi list, since they shouldn't be there, and this shows up as a UAF the next time we go through the byspi list. | 0% Низкий | 23 дня назад | |
 | CVE-2025-39965 xfrm: xfrm_alloc_spi shouldn't use 0 as SPI | CVSS3: 5.6 | 0% Низкий | 21 день назад |
| CVE-2025-39965 In the Linux kernel, the following vulnerability has been resolved: x ... | 0% Низкий | 23 дня назад | |
| GHSA-jc8g-4mch-vjcv In the Linux kernel, the following vulnerability has been resolved: xfrm: xfrm_alloc_spi shouldn't use 0 as SPI x->id.spi == 0 means "no SPI assigned", but since commit 94f39804d891 ("xfrm: Duplicate SPI Handling"), we now create states and add them to the byspi list with this value. __xfrm_state_delete doesn't remove those states from the byspi list, since they shouldn't be there, and this shows up as a UAF the next time we go through the byspi list. | 0% Низкий | 23 дня назад | |
 | BDU:2025-13242 Уязвимость функции xfrm_alloc_spi() модуля net/xfrm/xfrm_state.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 0% Низкий | 2 месяца назад |
| ELSA-2025-20719 ELSA-2025-20719: Unbreakable Enterprise kernel security update (IMPORTANT) | 13 дней назад |
Уязвимостей на страницу