Количество 16
Количество 16
CVE-2024-58240
In the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier.
CVE-2024-58240
In the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier.
CVE-2024-58240
In the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier.
CVE-2024-58240
In the Linux kernel, the following vulnerability has been resolved: t ...
GHSA-fpx7-665w-c5c9
In the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier.
BDU:2025-15231
Уязвимость функции tls_do_decryption() (net/tls/tls_sw.c) ядра операционной системы Linux, позволяющая нарушителю повысить свои привилегии
SUSE-SU-2025:03626-1
Security update for the Linux Kernel
SUSE-SU-2025:03614-1
Security update for the Linux Kernel
SUSE-SU-2025:03628-1
Security update for the Linux Kernel
SUSE-SU-2025:3751-1
Security update for the Linux Kernel
SUSE-SU-2025:03600-1
Security update for the Linux Kernel
SUSE-SU-2025:03615-1
Security update for the Linux Kernel
SUSE-SU-2025:03634-1
Security update for the Linux Kernel
SUSE-SU-2025:4141-1
Security update for the Linux Kernel
SUSE-SU-2025:4132-1
Security update for the Linux Kernel
SUSE-SU-2025:4057-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | CVE-2024-58240 In the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier. | 0% Низкий | 4 месяца назад | |
 | CVE-2024-58240 In the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier. | CVSS3: 7.3 | 0% Низкий | 4 месяца назад |
 | CVE-2024-58240 In the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier. | 0% Низкий | 4 месяца назад | |
| CVE-2024-58240 In the Linux kernel, the following vulnerability has been resolved: t ... | 0% Низкий | 4 месяца назад | |
| GHSA-fpx7-665w-c5c9 In the Linux kernel, the following vulnerability has been resolved: tls: separate no-async decryption request handling from async If we're not doing async, the handling is much simpler. There's no reference counting, we just need to wait for the completion to wake us up and return its result. We should preferably also use a separate crypto_wait. I'm not seeing a UAF as I did in the past, I think aec7961916f3 ("tls: fix race between async notify and socket close") took care of it. This will make the next fix easier. | 0% Низкий | 4 месяца назад | |
 | BDU:2025-15231 Уязвимость функции tls_do_decryption() (net/tls/tls_sw.c) ядра операционной системы Linux, позволяющая нарушителю повысить свои привилегии | CVSS3: 7.3 | 0% Низкий | почти 2 года назад |
 | SUSE-SU-2025:03626-1 Security update for the Linux Kernel | 3 месяца назад | ||
| SUSE-SU-2025:03614-1 Security update for the Linux Kernel | 3 месяца назад | ||
| SUSE-SU-2025:03628-1 Security update for the Linux Kernel | 3 месяца назад | ||
| SUSE-SU-2025:3751-1 Security update for the Linux Kernel | 2 месяца назад | ||
| SUSE-SU-2025:03600-1 Security update for the Linux Kernel | 3 месяца назад | ||
| SUSE-SU-2025:03615-1 Security update for the Linux Kernel | 3 месяца назад | ||
| SUSE-SU-2025:03634-1 Security update for the Linux Kernel | 3 месяца назад | ||
| SUSE-SU-2025:4141-1 Security update for the Linux Kernel | около 1 месяца назад | ||
| SUSE-SU-2025:4132-1 Security update for the Linux Kernel | около 1 месяца назад | ||
| SUSE-SU-2025:4057-1 Security update for the Linux Kernel | около 2 месяцев назад |
Уязвимостей на страницу