Поиск уязвимостей
Количество 30
Количество 30
BDU:2024-08317
Уязвимость функции kcm_sendmsg() реализации KCM (Kernel Connection Multiplexor) сокетов ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании
CVE-2024-44946
In the Linux kernel, the following vulnerability has been resolved: kcm: Serialise kcm_sendmsg() for the same socket. syzkaller reported UAF in kcm_release(). [0] The scenario is 1. Thread A builds a skb with MSG_MORE and sets kcm->seq_skb. 2. Thread A resumes building skb from kcm->seq_skb but is blocked by sk_stream_wait_memory() 3. Thread B calls sendmsg() concurrently, finishes building kcm->seq_skb and puts the skb to the write queue 4. Thread A faces an error and finally frees skb that is already in the write queue 5. kcm_release() does double-free the skb in the write queue When a thread is building a MSG_MORE skb, another thread must not touch it. Let's add a per-sk mutex and serialise kcm_sendmsg(). [0]: BUG: KASAN: slab-use-after-free in __skb_unlink include/linux/skbuff.h:2366 [inline] BUG: KASAN: slab-use-after-free in __skb_dequeue include/linux/skbuff.h:2385 [inline] BUG: KASAN: slab-use-after-free in __skb_queue_purge_reason include/linux/skbuff.h:3175 [inline] BUG: K...
CVE-2024-44946
In the Linux kernel, the following vulnerability has been resolved: kcm: Serialise kcm_sendmsg() for the same socket. syzkaller reported UAF in kcm_release(). [0] The scenario is 1. Thread A builds a skb with MSG_MORE and sets kcm->seq_skb. 2. Thread A resumes building skb from kcm->seq_skb but is blocked by sk_stream_wait_memory() 3. Thread B calls sendmsg() concurrently, finishes building kcm->seq_skb and puts the skb to the write queue 4. Thread A faces an error and finally frees skb that is already in the write queue 5. kcm_release() does double-free the skb in the write queue When a thread is building a MSG_MORE skb, another thread must not touch it. Let's add a per-sk mutex and serialise kcm_sendmsg(). [0]: BUG: KASAN: slab-use-after-free in __skb_unlink include/linux/skbuff.h:2366 [inline] BUG: KASAN: slab-use-after-free in __skb_dequeue include/linux/skbuff.h:2385 [inline] BUG: KASAN: slab-use-after-free in __skb_queue_purge_reason include/linux/skbuff.h:3175 [inline] BUG: K...
CVE-2024-44946
In the Linux kernel, the following vulnerability has been resolved: kcm: Serialise kcm_sendmsg() for the same socket. syzkaller reported UAF in kcm_release(). [0] The scenario is 1. Thread A builds a skb with MSG_MORE and sets kcm->seq_skb. 2. Thread A resumes building skb from kcm->seq_skb but is blocked by sk_stream_wait_memory() 3. Thread B calls sendmsg() concurrently, finishes building kcm->seq_skb and puts the skb to the write queue 4. Thread A faces an error and finally frees skb that is already in the write queue 5. kcm_release() does double-free the skb in the write queue When a thread is building a MSG_MORE skb, another thread must not touch it. Let's add a per-sk mutex and serialise kcm_sendmsg(). [0]: BUG: KASAN: slab-use-after-free in __skb_unlink include/linux/skbuff.h:2366 [inline] BUG: KASAN: slab-use-after-free in __skb_dequeue include/linux/skbuff.h:2385 [inline] BUG: KASAN: slab-use-after-free in __skb_queue_purge_reason include/li
CVE-2024-44946
CVE-2024-44946
In the Linux kernel, the following vulnerability has been resolved: k ...
GHSA-cw5c-5w4g-ff67
In the Linux kernel, the following vulnerability has been resolved: kcm: Serialise kcm_sendmsg() for the same socket. syzkaller reported UAF in kcm_release(). [0] The scenario is 1. Thread A builds a skb with MSG_MORE and sets kcm->seq_skb. 2. Thread A resumes building skb from kcm->seq_skb but is blocked by sk_stream_wait_memory() 3. Thread B calls sendmsg() concurrently, finishes building kcm->seq_skb and puts the skb to the write queue 4. Thread A faces an error and finally frees skb that is already in the write queue 5. kcm_release() does double-free the skb in the write queue When a thread is building a MSG_MORE skb, another thread must not touch it. Let's add a per-sk mutex and serialise kcm_sendmsg(). [0]: BUG: KASAN: slab-use-after-free in __skb_unlink include/linux/skbuff.h:2366 [inline] BUG: KASAN: slab-use-after-free in __skb_dequeue include/linux/skbuff.h:2385 [inline] BUG: KASAN: slab-use-after-free in __skb_queue_purge_reason include...
ROS-20250206-01
Множественные уязвимости kernel-lt
SUSE-SU-2024:3585-1
Security update for the Linux Kernel
SUSE-SU-2024:3565-1
Security update for the Linux Kernel
SUSE-SU-2024:3547-1
Security update for the Linux Kernel
ALT-PU-2024-11863
ALT-PU-2024-11863: package `kernel-image-std-def` update to version 6.1.107-alt0.p11.1
ALT-PU-2024-11855
ALT-PU-2024-11855: package `kernel-image-un-def` update to version 6.6.48-alt0.p11.1
ALT-PU-2024-13260
ALT-PU-2024-13260: package `kernel-image-pine` update to version 6.10.11-alt1
ALT-PU-2024-13121
ALT-PU-2024-13121: package `kernel-image-un-def` update to version 6.1.111-alt1
SUSE-SU-2024:3591-1
Security update for the Linux Kernel
SUSE-SU-2024:3559-1
Security update for the Linux Kernel
ELSA-2024-12813
ELSA-2024-12813: Unbreakable Enterprise kernel security update (IMPORTANT)
ELSA-2024-12868
ELSA-2024-12868: Unbreakable Enterprise kernel security update (IMPORTANT)
SUSE-SU-2024:3566-1
Security update for the Linux Kernel
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
BDU:2024-08317 Уязвимость функции kcm_sendmsg() реализации KCM (Kernel Connection Multiplexor) сокетов ядра операционной системы Linux, позволяющая нарушителю вызвать отказ в обслуживании | CVSS3: 5.5 | 1% Низкий | около 2 лет назад | |
CVE-2024-44946 In the Linux kernel, the following vulnerability has been resolved: kcm: Serialise kcm_sendmsg() for the same socket. syzkaller reported UAF in kcm_release(). [0] The scenario is 1. Thread A builds a skb with MSG_MORE and sets kcm->seq_skb. 2. Thread A resumes building skb from kcm->seq_skb but is blocked by sk_stream_wait_memory() 3. Thread B calls sendmsg() concurrently, finishes building kcm->seq_skb and puts the skb to the write queue 4. Thread A faces an error and finally frees skb that is already in the write queue 5. kcm_release() does double-free the skb in the write queue When a thread is building a MSG_MORE skb, another thread must not touch it. Let's add a per-sk mutex and serialise kcm_sendmsg(). [0]: BUG: KASAN: slab-use-after-free in __skb_unlink include/linux/skbuff.h:2366 [inline] BUG: KASAN: slab-use-after-free in __skb_dequeue include/linux/skbuff.h:2385 [inline] BUG: KASAN: slab-use-after-free in __skb_queue_purge_reason include/linux/skbuff.h:3175 [inline] BUG: K... | CVSS3: 5.5 | 1% Низкий | около 2 лет назад | |
CVE-2024-44946 In the Linux kernel, the following vulnerability has been resolved: kcm: Serialise kcm_sendmsg() for the same socket. syzkaller reported UAF in kcm_release(). [0] The scenario is 1. Thread A builds a skb with MSG_MORE and sets kcm->seq_skb. 2. Thread A resumes building skb from kcm->seq_skb but is blocked by sk_stream_wait_memory() 3. Thread B calls sendmsg() concurrently, finishes building kcm->seq_skb and puts the skb to the write queue 4. Thread A faces an error and finally frees skb that is already in the write queue 5. kcm_release() does double-free the skb in the write queue When a thread is building a MSG_MORE skb, another thread must not touch it. Let's add a per-sk mutex and serialise kcm_sendmsg(). [0]: BUG: KASAN: slab-use-after-free in __skb_unlink include/linux/skbuff.h:2366 [inline] BUG: KASAN: slab-use-after-free in __skb_dequeue include/linux/skbuff.h:2385 [inline] BUG: KASAN: slab-use-after-free in __skb_queue_purge_reason include/linux/skbuff.h:3175 [inline] BUG: K... | CVSS3: 5.5 | 1% Низкий | около 2 лет назад | |
CVE-2024-44946 In the Linux kernel, the following vulnerability has been resolved: kcm: Serialise kcm_sendmsg() for the same socket. syzkaller reported UAF in kcm_release(). [0] The scenario is 1. Thread A builds a skb with MSG_MORE and sets kcm->seq_skb. 2. Thread A resumes building skb from kcm->seq_skb but is blocked by sk_stream_wait_memory() 3. Thread B calls sendmsg() concurrently, finishes building kcm->seq_skb and puts the skb to the write queue 4. Thread A faces an error and finally frees skb that is already in the write queue 5. kcm_release() does double-free the skb in the write queue When a thread is building a MSG_MORE skb, another thread must not touch it. Let's add a per-sk mutex and serialise kcm_sendmsg(). [0]: BUG: KASAN: slab-use-after-free in __skb_unlink include/linux/skbuff.h:2366 [inline] BUG: KASAN: slab-use-after-free in __skb_dequeue include/linux/skbuff.h:2385 [inline] BUG: KASAN: slab-use-after-free in __skb_queue_purge_reason include/li | CVSS3: 5.5 | 1% Низкий | около 2 лет назад | |
CVSS3: 5.5 | 1% Низкий | около 2 лет назад | ||
CVE-2024-44946 In the Linux kernel, the following vulnerability has been resolved: k ... | CVSS3: 5.5 | 1% Низкий | около 2 лет назад | |
GHSA-cw5c-5w4g-ff67 In the Linux kernel, the following vulnerability has been resolved: kcm: Serialise kcm_sendmsg() for the same socket. syzkaller reported UAF in kcm_release(). [0] The scenario is 1. Thread A builds a skb with MSG_MORE and sets kcm->seq_skb. 2. Thread A resumes building skb from kcm->seq_skb but is blocked by sk_stream_wait_memory() 3. Thread B calls sendmsg() concurrently, finishes building kcm->seq_skb and puts the skb to the write queue 4. Thread A faces an error and finally frees skb that is already in the write queue 5. kcm_release() does double-free the skb in the write queue When a thread is building a MSG_MORE skb, another thread must not touch it. Let's add a per-sk mutex and serialise kcm_sendmsg(). [0]: BUG: KASAN: slab-use-after-free in __skb_unlink include/linux/skbuff.h:2366 [inline] BUG: KASAN: slab-use-after-free in __skb_dequeue include/linux/skbuff.h:2385 [inline] BUG: KASAN: slab-use-after-free in __skb_queue_purge_reason include... | CVSS3: 5.5 | 1% Низкий | около 2 лет назад | |
ROS-20250206-01 Множественные уязвимости kernel-lt | CVSS3: 7.8 | почти 2 года назад | ||
SUSE-SU-2024:3585-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:3565-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:3547-1 Security update for the Linux Kernel | около 2 лет назад | |||
ALT-PU-2024-11863 ALT-PU-2024-11863: package `kernel-image-std-def` update to version 6.1.107-alt0.p11.1 | CVSS3: 7.8 | около 2 лет назад | ||
ALT-PU-2024-11855 ALT-PU-2024-11855: package `kernel-image-un-def` update to version 6.6.48-alt0.p11.1 | CVSS3: 8.8 | около 2 лет назад | ||
ALT-PU-2024-13260 ALT-PU-2024-13260: package `kernel-image-pine` update to version 6.10.11-alt1 | CVSS3: 8.8 | около 2 лет назад | ||
ALT-PU-2024-13121 ALT-PU-2024-13121: package `kernel-image-un-def` update to version 6.1.111-alt1 | CVSS3: 8.8 | около 2 лет назад | ||
SUSE-SU-2024:3591-1 Security update for the Linux Kernel | около 2 лет назад | |||
SUSE-SU-2024:3559-1 Security update for the Linux Kernel | около 2 лет назад | |||
ELSA-2024-12813 ELSA-2024-12813: Unbreakable Enterprise kernel security update (IMPORTANT) | почти 2 года назад | |||
ELSA-2024-12868 ELSA-2024-12868: Unbreakable Enterprise kernel security update (IMPORTANT) | почти 2 года назад | |||
SUSE-SU-2024:3566-1 Security update for the Linux Kernel | около 2 лет назад |
Уязвимостей на страницу