Поиск уязвимостей
Количество 22
Количество 22
CVE-2024-57974
In the Linux kernel, the following vulnerability has been resolved: udp: Deal with race between UDP socket address change and rehash If a UDP socket changes its local address while it's receiving datagrams, as a result of connect(), there is a period during which a lookup operation might fail to find it, after the address is changed but before the secondary hash (port and address) and the four-tuple hash (local and remote ports and addresses) are updated. Secondary hash chains were introduced by commit 30fff9231fad ("udp: bind() optimisation") and, as a result, a rehash operation became needed to make a bound socket reachable again after a connect(). This operation was introduced by commit 719f835853a9 ("udp: add rehash on connect()") which isn't however a complete fix: the socket will be found once the rehashing completes, but not while it's pending. This is noticeable with a socat(1) server in UDP4-LISTEN mode, and a client sending datagrams to it. After the server receives the fi...
CVE-2024-57974
In the Linux kernel, the following vulnerability has been resolved: udp: Deal with race between UDP socket address change and rehash If a UDP socket changes its local address while it's receiving datagrams, as a result of connect(), there is a period during which a lookup operation might fail to find it, after the address is changed but before the secondary hash (port and address) and the four-tuple hash (local and remote ports and addresses) are updated. Secondary hash chains were introduced by commit 30fff9231fad ("udp: bind() optimisation") and, as a result, a rehash operation became needed to make a bound socket reachable again after a connect(). This operation was introduced by commit 719f835853a9 ("udp: add rehash on connect()") which isn't however a complete fix: the socket will be found once the rehashing completes, but not while it's pending. This is noticeable with a socat(1) server in UDP4-LISTEN mode, and a client sending datagrams to it. After the server receives the fi...
CVE-2024-57974
In the Linux kernel, the following vulnerability has been resolved: udp: Deal with race between UDP socket address change and rehash If a UDP socket changes its local address while it's receiving datagrams, as a result of connect(), there is a period during which a lookup operation might fail to find it, after the address is changed but before the secondary hash (port and address) and the four-tuple hash (local and remote ports and addresses) are updated. Secondary hash chains were introduced by commit 30fff9231fad ("udp: bind() optimisation") and, as a result, a rehash operation became needed to make a bound socket reachable again after a connect(). This operation was introduced by commit 719f835853a9 ("udp: add rehash on connect()") which isn't however a complete fix: the socket will be found once the rehashing completes, but not while it's pending. This is noticeable with a socat(1) server in UDP4-LISTEN mode, and a client sending datagrams to it. After the server receives the
CVE-2024-57974
udp: Deal with race between UDP socket address change and rehash
CVE-2024-57974
In the Linux kernel, the following vulnerability has been resolved: u ...
GHSA-hqjf-7m9j-v4qc
In the Linux kernel, the following vulnerability has been resolved: udp: Deal with race between UDP socket address change and rehash If a UDP socket changes its local address while it's receiving datagrams, as a result of connect(), there is a period during which a lookup operation might fail to find it, after the address is changed but before the secondary hash (port and address) and the four-tuple hash (local and remote ports and addresses) are updated. Secondary hash chains were introduced by commit 30fff9231fad ("udp: bind() optimisation") and, as a result, a rehash operation became needed to make a bound socket reachable again after a connect(). This operation was introduced by commit 719f835853a9 ("udp: add rehash on connect()") which isn't however a complete fix: the socket will be found once the rehashing completes, but not while it's pending. This is noticeable with a socat(1) server in UDP4-LISTEN mode, and a client sending datagrams to it. After the server receives t...
BDU:2026-03291
Уязвимость функции udp_ehashfn() модуля net/ipv4/udp.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
RLSA-2026:90365
Important: kernel security, bug fix, and enhancement update
ELSA-2026-90365
ELSA-2026-90365: kernel security, bug fix, and enhancement update (IMPORTANT)
SUSE-SU-2025:1177-1
Security update for the Linux Kernel
SUSE-SU-2025:1180-1
Security update for the Linux Kernel
SUSE-SU-2025:1178-1
Security update for the Linux Kernel
ALT-PU-2025-16502
ALT-PU-2025-16502: package `kernel-image-6.12` update to version 6.12.14-alt1
ALT-PU-2025-16450
ALT-PU-2025-16450: package `kernel-image-pine` update to version 6.12.14-alt1
SUSE-SU-2025:01951-1
Security update for the Linux Kernel
SUSE-SU-2025:01967-1
Security update for the Linux Kernel
ALT-PU-2025-16461
ALT-PU-2025-16461: package `kernel-image-rt` update to version 6.12.16-alt1
SUSE-SU-2025:01919-1
Security update for the Linux Kernel
ELSA-2025-20530
ELSA-2025-20530: Unbreakable Enterprise kernel security update (IMPORTANT)
ELSA-2025-20480
ELSA-2025-20480: Unbreakable Enterprise kernel security update (IMPORTANT)
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
CVE-2024-57974 In the Linux kernel, the following vulnerability has been resolved: udp: Deal with race between UDP socket address change and rehash If a UDP socket changes its local address while it's receiving datagrams, as a result of connect(), there is a period during which a lookup operation might fail to find it, after the address is changed but before the secondary hash (port and address) and the four-tuple hash (local and remote ports and addresses) are updated. Secondary hash chains were introduced by commit 30fff9231fad ("udp: bind() optimisation") and, as a result, a rehash operation became needed to make a bound socket reachable again after a connect(). This operation was introduced by commit 719f835853a9 ("udp: add rehash on connect()") which isn't however a complete fix: the socket will be found once the rehashing completes, but not while it's pending. This is noticeable with a socat(1) server in UDP4-LISTEN mode, and a client sending datagrams to it. After the server receives the fi... | CVSS3: 4.7 | 0% Низкий | больше 1 года назад | |
CVE-2024-57974 In the Linux kernel, the following vulnerability has been resolved: udp: Deal with race between UDP socket address change and rehash If a UDP socket changes its local address while it's receiving datagrams, as a result of connect(), there is a period during which a lookup operation might fail to find it, after the address is changed but before the secondary hash (port and address) and the four-tuple hash (local and remote ports and addresses) are updated. Secondary hash chains were introduced by commit 30fff9231fad ("udp: bind() optimisation") and, as a result, a rehash operation became needed to make a bound socket reachable again after a connect(). This operation was introduced by commit 719f835853a9 ("udp: add rehash on connect()") which isn't however a complete fix: the socket will be found once the rehashing completes, but not while it's pending. This is noticeable with a socat(1) server in UDP4-LISTEN mode, and a client sending datagrams to it. After the server receives the fi... | CVSS3: 4.7 | 0% Низкий | больше 1 года назад | |
CVE-2024-57974 In the Linux kernel, the following vulnerability has been resolved: udp: Deal with race between UDP socket address change and rehash If a UDP socket changes its local address while it's receiving datagrams, as a result of connect(), there is a period during which a lookup operation might fail to find it, after the address is changed but before the secondary hash (port and address) and the four-tuple hash (local and remote ports and addresses) are updated. Secondary hash chains were introduced by commit 30fff9231fad ("udp: bind() optimisation") and, as a result, a rehash operation became needed to make a bound socket reachable again after a connect(). This operation was introduced by commit 719f835853a9 ("udp: add rehash on connect()") which isn't however a complete fix: the socket will be found once the rehashing completes, but not while it's pending. This is noticeable with a socat(1) server in UDP4-LISTEN mode, and a client sending datagrams to it. After the server receives the | CVSS3: 4.7 | 0% Низкий | больше 1 года назад | |
CVE-2024-57974 udp: Deal with race between UDP socket address change and rehash | CVSS3: 4.7 | 0% Низкий | 19 дней назад | |
CVE-2024-57974 In the Linux kernel, the following vulnerability has been resolved: u ... | CVSS3: 4.7 | 0% Низкий | больше 1 года назад | |
GHSA-hqjf-7m9j-v4qc In the Linux kernel, the following vulnerability has been resolved: udp: Deal with race between UDP socket address change and rehash If a UDP socket changes its local address while it's receiving datagrams, as a result of connect(), there is a period during which a lookup operation might fail to find it, after the address is changed but before the secondary hash (port and address) and the four-tuple hash (local and remote ports and addresses) are updated. Secondary hash chains were introduced by commit 30fff9231fad ("udp: bind() optimisation") and, as a result, a rehash operation became needed to make a bound socket reachable again after a connect(). This operation was introduced by commit 719f835853a9 ("udp: add rehash on connect()") which isn't however a complete fix: the socket will be found once the rehashing completes, but not while it's pending. This is noticeable with a socat(1) server in UDP4-LISTEN mode, and a client sending datagrams to it. After the server receives t... | CVSS3: 4.7 | 0% Низкий | больше 1 года назад | |
BDU:2026-03291 Уязвимость функции udp_ehashfn() модуля net/ipv4/udp.c ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 4.7 | 0% Низкий | почти 2 года назад | |
RLSA-2026:90365 Important: kernel security, bug fix, and enhancement update | 10 дней назад | |||
ELSA-2026-90365 ELSA-2026-90365: kernel security, bug fix, and enhancement update (IMPORTANT) | 13 дней назад | |||
SUSE-SU-2025:1177-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:1180-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:1178-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2025-16502 ALT-PU-2025-16502: package `kernel-image-6.12` update to version 6.12.14-alt1 | CVSS3: 8.8 | больше 1 года назад | ||
ALT-PU-2025-16450 ALT-PU-2025-16450: package `kernel-image-pine` update to version 6.12.14-alt1 | CVSS3: 8.8 | больше 1 года назад | ||
SUSE-SU-2025:01951-1 Security update for the Linux Kernel | больше 1 года назад | |||
SUSE-SU-2025:01967-1 Security update for the Linux Kernel | больше 1 года назад | |||
ALT-PU-2025-16461 ALT-PU-2025-16461: package `kernel-image-rt` update to version 6.12.16-alt1 | CVSS3: 9.8 | больше 1 года назад | ||
SUSE-SU-2025:01919-1 Security update for the Linux Kernel | больше 1 года назад | |||
ELSA-2025-20530 ELSA-2025-20530: Unbreakable Enterprise kernel security update (IMPORTANT) | около 1 года назад | |||
ELSA-2025-20480 ELSA-2025-20480: Unbreakable Enterprise kernel security update (IMPORTANT) | больше 1 года назад |
Уязвимостей на страницу