https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 00:58:24 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-10806 bdu:2025-10806 https://cve.radiocsirt.org/vuln/bdu:2025-10806 https://cve.radiocsirt.org/vuln/bell-cve-2025-38475 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2025-38475 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0698 certfr-2025-avi-0698 https://cve.radiocsirt.org/vuln/certfr-2025-avi-0698 https://cve.radiocsirt.org/vuln/euvd-2026-347060 EUVD-2026-347060 https://cve.radiocsirt.org/vuln/euvd-2026-347060 https://cve.radiocsirt.org/vuln/fkie_cve-2025-38475 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>smc: Fix various oops due to inet_sock type confusion.</p> <p>syzbot reported weird splats [0][1] in cipso_v4_sock_setattr() while freeing inet_sk(sk)-&gt;inet_opt.</p> <p>The address was freed multiple times even though it was read-only memory.</p> <p>cipso_v4_sock_setattr() did nothing wrong, and the root cause was type confusion.</p> <p>The cited commit made it possible to create smc_sock as an INET socket.</p> <p>The issue is that struct smc_sock does not have struct inet_sock as the first member but hijacks AF_INET and AF_INET6 sk_family, which confuses various places.</p> <p>In this case, inet_sock.inet_opt was actually smc_sock.clcsk_data_ready(), which is an address of a function in the text segment.</p> <p>$ pahole -C inet_sock vmlinux struct inet_sock { ... struct ip_options_rcu * inet_opt; /* 784 8 */</p> <p>$ pahole -C smc_sock vmlinux struct smc_sock { ... void (*clcsk_data_ready)(struct sock *); /* 784 8 */</p> <p>The same issue for another field was reported before. [2][3]</p> <p>At that time, an ugly hack was suggested [4], but it makes both INET and SMC code error-prone and hard to change.</p> <p>Also, yet another variant was fixed by a hacky commit 98d4435efcbf3 (&#34;net/smc: prevent NULL pointer dereference in txopt_get&#34;).</p> <p>Instead of papering over the root cause by such hacks, we should not allow non-INET socket to reuse the INET infra.</p> <p>Let&#39;s add inet_sock as the first member o…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>smc: Fix various oops due to inet_sock type confusion.</p> <p>syzbot reported weird splats [0][1] in cipso_v4_sock_setattr() while freeing inet_sk(sk)-&gt;inet_opt.</p> <p>The address was freed multiple times even though it was read-only memory.</p> <p>cipso_v4_sock_setattr() did nothing wrong, and the root cause was type confusion.</p> <p>The cited commit made it possible to create smc_sock as an INET socket.</p> <p>The issue is that struct smc_sock does not have struct inet_sock as the first member but hijacks AF_INET and AF_INET6 sk_family, which confuses various places.</p> <p>In this case, inet_sock.inet_opt was actually smc_sock.clcsk_data_ready(), which is an address of a function in the text segment.</p> <p>$ pahole -C inet_sock vmlinux struct inet_sock { ... struct ip_options_rcu * inet_opt; /* 784 8 */</p> <p>$ pahole -C smc_sock vmlinux struct smc_sock { ... void (*clcsk_data_ready)(struct sock *); /* 784 8 */</p> <p>The same issue for another field was reported before. [2][3]</p> <p>At that time, an ugly hack was suggested [4], but it makes both INET and SMC code error-prone and hard to change.</p> <p>Also, yet another variant was fixed by a hacky commit 98d4435efcbf3 (&#34;net/smc: prevent NULL pointer dereference in txopt_get&#34;).</p> <p>Instead of papering over the root cause by such hacks, we should not allow non-INET socket to reuse the INET infra.</p> <p>Let&#39;s add inet_sock as the first member o…</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-38475 https://cve.radiocsirt.org/vuln/ghsa-wfpw-m32p-qqfp <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>smc: Fix various oops due to inet_sock type confusion.</p> <p>syzbot reported weird splats [0][1] in cipso_v4_sock_setattr() while freeing inet_sk(sk)-&gt;inet_opt.</p> <p>The address was freed multiple times even though it was read-only memory.</p> <p>cipso_v4_sock_setattr() did nothing wrong, and the root cause was type confusion.</p> <p>The cited commit made it possible to create smc_sock as an INET socket.</p> <p>The issue is that struct smc_sock does not have struct inet_sock as the first member but hijacks AF_INET and AF_INET6 sk_family, which confuses various places.</p> <p>In this case, inet_sock.inet_opt was actually smc_sock.clcsk_data_ready(), which is an address of a function in the text segment.</p> <p>$ pahole -C inet_sock vmlinux struct inet_sock { ... struct ip_options_rcu * inet_opt; /* 784 8 */</p> <p>$ pahole -C smc_sock vmlinux struct smc_sock { ... void (*clcsk_data_ready)(struct sock *); /* 784 8 */</p> <p>The same issue for another field was reported before. [2][3]</p> <p>At that time, an ugly hack was suggested [4], but it makes both INET and SMC code error-prone and hard to change.</p> <p>Also, yet another variant was fixed by a hacky commit 98d4435efcbf3 (&#34;net/smc: prevent NULL pointer dereference in txopt_get&#34;).</p> <p>Instead of papering over the root cause by such hacks, we should not allow non-INET socket to reuse the INET infra.</p> <p>Let&#39;s add inet_sock as the first member o…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>smc: Fix various oops due to inet_sock type confusion.</p> <p>syzbot reported weird splats [0][1] in cipso_v4_sock_setattr() while freeing inet_sk(sk)-&gt;inet_opt.</p> <p>The address was freed multiple times even though it was read-only memory.</p> <p>cipso_v4_sock_setattr() did nothing wrong, and the root cause was type confusion.</p> <p>The cited commit made it possible to create smc_sock as an INET socket.</p> <p>The issue is that struct smc_sock does not have struct inet_sock as the first member but hijacks AF_INET and AF_INET6 sk_family, which confuses various places.</p> <p>In this case, inet_sock.inet_opt was actually smc_sock.clcsk_data_ready(), which is an address of a function in the text segment.</p> <p>$ pahole -C inet_sock vmlinux struct inet_sock { ... struct ip_options_rcu * inet_opt; /* 784 8 */</p> <p>$ pahole -C smc_sock vmlinux struct smc_sock { ... void (*clcsk_data_ready)(struct sock *); /* 784 8 */</p> <p>The same issue for another field was reported before. [2][3]</p> <p>At that time, an ugly hack was suggested [4], but it makes both INET and SMC code error-prone and hard to change.</p> <p>Also, yet another variant was fixed by a hacky commit 98d4435efcbf3 (&#34;net/smc: prevent NULL pointer dereference in txopt_get&#34;).</p> <p>Instead of papering over the root cause by such hacks, we should not allow non-INET socket to reuse the INET infra.</p> <p>Let&#39;s add inet_sock as the first member o…</p> https://cve.radiocsirt.org/vuln/ghsa-wfpw-m32p-qqfp https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-1 https://cve.radiocsirt.org/vuln/suse-su-2025:02853-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://cve.radiocsirt.org/vuln/suse-su-2025:02853-1 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38475 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 87 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: smc: Fix various oops due to inet_sock type confusion. syzbot reported weird splats [0][1] in cipso_v4_sock_setattr() while freeing inet_sk(sk)-&gt;inet_opt. The address was freed multiple times even though it was read-only memory. cipso_v4_sock_setattr() did nothing wrong, and the root cause was type confusion. The cited commit made it possible to create smc_sock as an INET socket. The issue is that struct smc_sock does not have struct inet_sock as the first member but hijacks AF_INET and AF_INET6 sk_family, which confuses various places. In this case, inet_sock.inet_opt was actually smc_sock.clcsk_data_ready(), which is an address of a function in the text segment. $ pahole -C inet_sock vmlinux struct inet_sock { ... struct ip_options_rcu * inet_opt; /* 784 8 */ $ pahole -C smc_sock vmlinux struct smc_sock { ... void (*clcsk_data_ready)(struct sock *); /* 784 8 */ The same issue for another field was reported before. [2][3] At that time, an ugly hack was suggested [4], but it makes both INET and SMC code error-prone and hard to change. Also, yet another variant was fixed by a hacky commit 98d4435efcbf3 (&#34;net/smc: prevent NULL pointer dereference in txopt_get&#34;). Instead of papering over the root cause by such hacks, we should not allow non-INET socket to reuse the INET infra. Let&#39;s add inet_sock as the first member of smc_sock. [0…</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 87 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: smc: Fix various oops due to inet_sock type confusion. syzbot reported weird splats [0][1] in cipso_v4_sock_setattr() while freeing inet_sk(sk)-&gt;inet_opt. The address was freed multiple times even though it was read-only memory. cipso_v4_sock_setattr() did nothing wrong, and the root cause was type confusion. The cited commit made it possible to create smc_sock as an INET socket. The issue is that struct smc_sock does not have struct inet_sock as the first member but hijacks AF_INET and AF_INET6 sk_family, which confuses various places. In this case, inet_sock.inet_opt was actually smc_sock.clcsk_data_ready(), which is an address of a function in the text segment. $ pahole -C inet_sock vmlinux struct inet_sock { ... struct ip_options_rcu * inet_opt; /* 784 8 */ $ pahole -C smc_sock vmlinux struct smc_sock { ... void (*clcsk_data_ready)(struct sock *); /* 784 8 */ The same issue for another field was reported before. [2][3] At that time, an ugly hack was suggested [4], but it makes both INET and SMC code error-prone and hard to change. Also, yet another variant was fixed by a hacky commit 98d4435efcbf3 (&#34;net/smc: prevent NULL pointer dereference in txopt_get&#34;). Instead of papering over the root cause by such hacks, we should not allow non-INET socket to reuse the INET infra. Let&#39;s add inet_sock as the first member of smc_sock. [0…</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38475 https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1665 <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht spezifizierte Angriffe durchzuführen.</p> <p>Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder andere nicht spezifizierte Angriffe durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1665