https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 02:46:54 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-10213 bdu:2026-10213 https://cve.radiocsirt.org/vuln/bdu:2026-10213 https://cve.radiocsirt.org/vuln/bell-cve-2023-53825 <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2023-53825 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108 certfr-2026-avi-0108 https://cve.radiocsirt.org/vuln/certfr-2026-avi-0108 https://cve.radiocsirt.org/vuln/euvd-2026-312275 EUVD-2026-312275 https://cve.radiocsirt.org/vuln/euvd-2026-312275 https://cve.radiocsirt.org/vuln/fkie_cve-2023-53825 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg().</p> <p>syzkaller found a memory leak in kcm_sendmsg(), and commit c821a88bd720 (&#34;kcm: Fix memory leak in error path of kcm_sendmsg()&#34;) suppressed it by updating kcm_tx_msg(head)-&gt;last_skb if partial data is copied so that the following sendmsg() will resume from the skb.</p> <p>However, we cannot know how many bytes were copied when we get the error. Thus, we could mess up the MSG_MORE queue.</p> <p>When kcm_sendmsg() fails for SOCK_DGRAM, we should purge the queue as we do so for UDP by udp_flush_pending_frames().</p> <p>Even without this change, when the error occurred, the following sendmsg() resumed from a wrong skb and the queue was messed up. However, we have yet to get such a report, and only syzkaller stumbled on it. So, this can be changed safely.</p> <p>Note this does not change SOCK_SEQPACKET behaviour.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg().</p> <p>syzkaller found a memory leak in kcm_sendmsg(), and commit c821a88bd720 (&#34;kcm: Fix memory leak in error path of kcm_sendmsg()&#34;) suppressed it by updating kcm_tx_msg(head)-&gt;last_skb if partial data is copied so that the following sendmsg() will resume from the skb.</p> <p>However, we cannot know how many bytes were copied when we get the error. Thus, we could mess up the MSG_MORE queue.</p> <p>When kcm_sendmsg() fails for SOCK_DGRAM, we should purge the queue as we do so for UDP by udp_flush_pending_frames().</p> <p>Even without this change, when the error occurred, the following sendmsg() resumed from a wrong skb and the queue was messed up. However, we have yet to get such a report, and only syzkaller stumbled on it. So, this can be changed safely.</p> <p>Note this does not change SOCK_SEQPACKET behaviour.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2023-53825 https://cve.radiocsirt.org/vuln/ghsa-qqwx-6fr4-mfj2 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg().</p> <p>syzkaller found a memory leak in kcm_sendmsg(), and commit c821a88bd720 (&#34;kcm: Fix memory leak in error path of kcm_sendmsg()&#34;) suppressed it by updating kcm_tx_msg(head)-&gt;last_skb if partial data is copied so that the following sendmsg() will resume from the skb.</p> <p>However, we cannot know how many bytes were copied when we get the error. Thus, we could mess up the MSG_MORE queue.</p> <p>When kcm_sendmsg() fails for SOCK_DGRAM, we should purge the queue as we do so for UDP by udp_flush_pending_frames().</p> <p>Even without this change, when the error occurred, the following sendmsg() resumed from a wrong skb and the queue was messed up. However, we have yet to get such a report, and only syzkaller stumbled on it. So, this can be changed safely.</p> <p>Note this does not change SOCK_SEQPACKET behaviour.</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg().</p> <p>syzkaller found a memory leak in kcm_sendmsg(), and commit c821a88bd720 (&#34;kcm: Fix memory leak in error path of kcm_sendmsg()&#34;) suppressed it by updating kcm_tx_msg(head)-&gt;last_skb if partial data is copied so that the following sendmsg() will resume from the skb.</p> <p>However, we cannot know how many bytes were copied when we get the error. Thus, we could mess up the MSG_MORE queue.</p> <p>When kcm_sendmsg() fails for SOCK_DGRAM, we should purge the queue as we do so for UDP by udp_flush_pending_frames().</p> <p>Even without this change, when the error occurred, the following sendmsg() resumed from a wrong skb and the queue was messed up. However, we have yet to get such a report, and only syzkaller stumbled on it. So, this can be changed safely.</p> <p>Note this does not change SOCK_SEQPACKET behaviour.</p> https://cve.radiocsirt.org/vuln/ghsa-qqwx-6fr4-mfj2 https://cve.radiocsirt.org/vuln/suse-su-2026:0278-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2026:0278-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53825 <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 162 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg(). syzkaller found a memory leak in kcm_sendmsg(), and commit c821a88bd720 (&#34;kcm: Fix memory leak in error path of kcm_sendmsg()&#34;) suppressed it by updating kcm_tx_msg(head)-&gt;last_skb if partial data is copied so that the following sendmsg() will resume from the skb. However, we cannot know how many bytes were copied when we get the error. Thus, we could mess up the MSG_MORE queue. When kcm_sendmsg() fails for SOCK_DGRAM, we should purge the queue as we do so for UDP by udp_flush_pending_frames(). Even without this change, when the error occurred, the following sendmsg() resumed from a wrong skb and the queue was messed up. However, we have yet to get such a report, and only syzkaller stumbled on it. So, this can be changed safely. Note this does not change SOCK_SEQPACKET behaviour.</p> <p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 162 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: kcm: Fix error handling for SOCK_DGRAM in kcm_sendmsg(). syzkaller found a memory leak in kcm_sendmsg(), and commit c821a88bd720 (&#34;kcm: Fix memory leak in error path of kcm_sendmsg()&#34;) suppressed it by updating kcm_tx_msg(head)-&gt;last_skb if partial data is copied so that the following sendmsg() will resume from the skb. However, we cannot know how many bytes were copied when we get the error. Thus, we could mess up the MSG_MORE queue. When kcm_sendmsg() fails for SOCK_DGRAM, we should purge the queue as we do so for UDP by udp_flush_pending_frames(). Even without this change, when the error occurred, the following sendmsg() resumed from a wrong skb and the queue was messed up. However, we have yet to get such a report, and only syzkaller stumbled on it. So, this can be changed safely. Note this does not change SOCK_SEQPACKET behaviour.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-53825 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2765 <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2765