https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 11:41:02 +0000 https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-0449 CERTFR-2025-AVI-0449 https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-0449 https://vulnerability.circl.lu/vuln/bdu:2025-06238 bdu:2025-06238 https://vulnerability.circl.lu/vuln/bdu:2025-06238 https://vulnerability.circl.lu/vuln/bell-cve-2023-52986 <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p> https://vulnerability.circl.lu/vuln/bell-cve-2023-52986 https://vulnerability.circl.lu/vuln/fkie_cve-2023-52986 <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener</p> <p>A listening socket linked to a sockmap has its sk_prot overridden. It points to one of the struct proto variants in tcp_bpf_prots. The variant depends on the socket&#39;s family and which sockmap programs are attached.</p> <p>A child socket cloned from a TCP listener initially inherits their sk_prot. But before cloning is finished, we restore the child&#39;s proto to the listener&#39;s original non-tcp_bpf_prots one. This happens in tcp_create_openreq_child -&gt; tcp_bpf_clone.</p> <p>Today, in tcp_bpf_clone we detect if the child&#39;s proto should be restored by checking only for the TCP_BPF_BASE proto variant. This is not correct. The sk_prot of listening socket linked to a sockmap can point to to any variant in tcp_bpf_prots.</p> <p>If the listeners sk_prot happens to be not the TCP_BPF_BASE variant, then the child socket unintentionally is left if the inherited sk_prot by tcp_bpf_clone.</p> <p>This leads to issues like infinite recursion on close [1], because the child state is otherwise not set up for use with tcp_bpf_prot operations.</p> <p>Adjust the check in tcp_bpf_clone to detect all of tcp_bpf_prots variants.</p> <p>Note that it wouldn&#39;t be sufficient to check the socket state when overriding the sk_prot in tcp_bpf_update_proto in order to always use the TCP_BPF_BASE variant for listening sockets. Since commit b8b8315e39ff (&#34;bpf, sockmap: Remove unhash handler for BPF sockmap usag…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener</p> <p>A listening socket linked to a sockmap has its sk_prot overridden. It points to one of the struct proto variants in tcp_bpf_prots. The variant depends on the socket&#39;s family and which sockmap programs are attached.</p> <p>A child socket cloned from a TCP listener initially inherits their sk_prot. But before cloning is finished, we restore the child&#39;s proto to the listener&#39;s original non-tcp_bpf_prots one. This happens in tcp_create_openreq_child -&gt; tcp_bpf_clone.</p> <p>Today, in tcp_bpf_clone we detect if the child&#39;s proto should be restored by checking only for the TCP_BPF_BASE proto variant. This is not correct. The sk_prot of listening socket linked to a sockmap can point to to any variant in tcp_bpf_prots.</p> <p>If the listeners sk_prot happens to be not the TCP_BPF_BASE variant, then the child socket unintentionally is left if the inherited sk_prot by tcp_bpf_clone.</p> <p>This leads to issues like infinite recursion on close [1], because the child state is otherwise not set up for use with tcp_bpf_prot operations.</p> <p>Adjust the check in tcp_bpf_clone to detect all of tcp_bpf_prots variants.</p> <p>Note that it wouldn&#39;t be sufficient to check the socket state when overriding the sk_prot in tcp_bpf_update_proto in order to always use the TCP_BPF_BASE variant for listening sockets. Since commit b8b8315e39ff (&#34;bpf, sockmap: Remove unhash handler for BPF sockmap usag…</p> https://vulnerability.circl.lu/vuln/fkie_cve-2023-52986 https://vulnerability.circl.lu/vuln/ghsa-3m27-46p7-w7mh <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener</p> <p>A listening socket linked to a sockmap has its sk_prot overridden. It points to one of the struct proto variants in tcp_bpf_prots. The variant depends on the socket&#39;s family and which sockmap programs are attached.</p> <p>A child socket cloned from a TCP listener initially inherits their sk_prot. But before cloning is finished, we restore the child&#39;s proto to the listener&#39;s original non-tcp_bpf_prots one. This happens in tcp_create_openreq_child -&gt; tcp_bpf_clone.</p> <p>Today, in tcp_bpf_clone we detect if the child&#39;s proto should be restored by checking only for the TCP_BPF_BASE proto variant. This is not correct. The sk_prot of listening socket linked to a sockmap can point to to any variant in tcp_bpf_prots.</p> <p>If the listeners sk_prot happens to be not the TCP_BPF_BASE variant, then the child socket unintentionally is left if the inherited sk_prot by tcp_bpf_clone.</p> <p>This leads to issues like infinite recursion on close [1], because the child state is otherwise not set up for use with tcp_bpf_prot operations.</p> <p>Adjust the check in tcp_bpf_clone to detect all of tcp_bpf_prots variants.</p> <p>Note that it wouldn&#39;t be sufficient to check the socket state when overriding the sk_prot in tcp_bpf_update_proto in order to always use the TCP_BPF_BASE variant for listening sockets. Since commit b8b8315e39ff (&#34;bpf, sockmap: Remove unhash handler for BPF sockmap usag…</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener</p> <p>A listening socket linked to a sockmap has its sk_prot overridden. It points to one of the struct proto variants in tcp_bpf_prots. The variant depends on the socket&#39;s family and which sockmap programs are attached.</p> <p>A child socket cloned from a TCP listener initially inherits their sk_prot. But before cloning is finished, we restore the child&#39;s proto to the listener&#39;s original non-tcp_bpf_prots one. This happens in tcp_create_openreq_child -&gt; tcp_bpf_clone.</p> <p>Today, in tcp_bpf_clone we detect if the child&#39;s proto should be restored by checking only for the TCP_BPF_BASE proto variant. This is not correct. The sk_prot of listening socket linked to a sockmap can point to to any variant in tcp_bpf_prots.</p> <p>If the listeners sk_prot happens to be not the TCP_BPF_BASE variant, then the child socket unintentionally is left if the inherited sk_prot by tcp_bpf_clone.</p> <p>This leads to issues like infinite recursion on close [1], because the child state is otherwise not set up for use with tcp_bpf_prot operations.</p> <p>Adjust the check in tcp_bpf_clone to detect all of tcp_bpf_prots variants.</p> <p>Note that it wouldn&#39;t be sufficient to check the socket state when overriding the sk_prot in tcp_bpf_update_proto in order to always use the TCP_BPF_BASE variant for listening sockets. Since commit b8b8315e39ff (&#34;bpf, sockmap: Remove unhash handler for BPF sockmap usag…</p> https://vulnerability.circl.lu/vuln/ghsa-3m27-46p7-w7mh https://vulnerability.circl.lu/vuln/rhsa-2023:6583 <p>kernel: seg6: fix the iif in the IPv6 socket control block Kernel: race when faulting a device private page in memory manager kernel: use-after-free in l1oip timer handlers kernel: Rate limit overflow messages in r8152 in intr_callback kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c kernel: perf: Fix perf_pending_task() UaF kernel: gpiolib: fix memory leak in gpiochip_setup_dev() kernel: memcg: fix possible use-after-free in memcg_write_event_control() kernel: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths kernel: char: tpm: Protect tpm_pm_suspend with locks kernel: ixgbevf: Fix resource leak in ixgbevf_init_module() kernel: dax: make sure inodes are flushed before destroy cache kernel: watch_queue: Actually free the watch kernel: watch_queue: Fix NULL dereference in error cleanup kernel: rtc: pl031: fix rtc features null pointer dereference kernel: tpm: fix reference counting for struct tpm_chip kernel: NFSv4: Don&#39;t hold the layoutget locks across multiple RPC calls kernel: xprtrdma: treat all calls not a bcall when bc_serv is NULL kernel: net: ipv6: unexport __init-annotated seg6_hmac_init() kernel: af_unix: Fix a data-race in unix_dgram_peer_wake_me(). kernel: regulator: scmi: Fix refcount leak in scmi_regulator_probe kernel: mm/mempolicy: fix uninit-v…</p> <p>kernel: seg6: fix the iif in the IPv6 socket control block Kernel: race when faulting a device private page in memory manager kernel: use-after-free in l1oip timer handlers kernel: Rate limit overflow messages in r8152 in intr_callback kernel: vmwgfx: use-after-free in vmw_cmd_res_check kernel: vmwgfx: use-after-free in vmw_execbuf_tie_context hw: Intel: Gather Data Sampling (GDS) side channel vulnerability kernel: Information leak in l2cap_parse_conf_req in net/bluetooth/l2cap_core.c kernel: perf: Fix perf_pending_task() UaF kernel: gpiolib: fix memory leak in gpiochip_setup_dev() kernel: memcg: fix possible use-after-free in memcg_write_event_control() kernel: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths kernel: char: tpm: Protect tpm_pm_suspend with locks kernel: ixgbevf: Fix resource leak in ixgbevf_init_module() kernel: dax: make sure inodes are flushed before destroy cache kernel: watch_queue: Actually free the watch kernel: watch_queue: Fix NULL dereference in error cleanup kernel: rtc: pl031: fix rtc features null pointer dereference kernel: tpm: fix reference counting for struct tpm_chip kernel: NFSv4: Don&#39;t hold the layoutget locks across multiple RPC calls kernel: xprtrdma: treat all calls not a bcall when bc_serv is NULL kernel: net: ipv6: unexport __init-annotated seg6_hmac_init() kernel: af_unix: Fix a data-race in unix_dgram_peer_wake_me(). kernel: regulator: scmi: Fix refcount leak in scmi_regulator_probe kernel: mm/mempolicy: fix uninit-v…</p> https://vulnerability.circl.lu/vuln/rhsa-2023:6583 https://vulnerability.circl.lu/vuln/suse-su-2025:01620-1 <p>Security update for the Linux Kernel</p> <p>Security update for the Linux Kernel</p> https://vulnerability.circl.lu/vuln/suse-su-2025:01620-1 https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-52986 <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 95 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener A listening socket linked to a sockmap has its sk_prot overridden. It points to one of the struct proto variants in tcp_bpf_prots. The variant depends on the socket&#39;s family and which sockmap programs are attached. A child socket cloned from a TCP listener initially inherits their sk_prot. But before cloning is finished, we restore the child&#39;s proto to the listener&#39;s original non-tcp_bpf_prots one. This happens in tcp_create_openreq_child -&gt; tcp_bpf_clone. Today, in tcp_bpf_clone we detect if the child&#39;s proto should be restored by checking only for the TCP_BPF_BASE proto variant. This is not correct. The sk_prot of listening socket linked to a sockmap can point to to any variant in tcp_bpf_prots. If the listeners sk_prot happens to be not the TCP_BPF_BASE variant, then the child socket unintentionally is left if the inherited sk_prot by tcp_bpf_clone. This leads to issues like infinite recursion on close [1], because the child state is otherwise not set up for use with tcp_bpf_prot operations. Adjust the check in tcp_bpf_clone to detect all of tcp_bpf_prots variants. Note that it wouldn&#39;t be sufficient to check the socket state when overriding the sk_prot in tcp_bpf_update_proto in order to always use the TCP_BPF_BASE variant for listening sockets. Since commit b8b8315e39ff (&#34;bpf, sockmap: Remove unhash handler for BPF sockmap usage&#34;) it i…</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 95 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Check for any of tcp_bpf_prots when cloning a listener A listening socket linked to a sockmap has its sk_prot overridden. It points to one of the struct proto variants in tcp_bpf_prots. The variant depends on the socket&#39;s family and which sockmap programs are attached. A child socket cloned from a TCP listener initially inherits their sk_prot. But before cloning is finished, we restore the child&#39;s proto to the listener&#39;s original non-tcp_bpf_prots one. This happens in tcp_create_openreq_child -&gt; tcp_bpf_clone. Today, in tcp_bpf_clone we detect if the child&#39;s proto should be restored by checking only for the TCP_BPF_BASE proto variant. This is not correct. The sk_prot of listening socket linked to a sockmap can point to to any variant in tcp_bpf_prots. If the listeners sk_prot happens to be not the TCP_BPF_BASE variant, then the child socket unintentionally is left if the inherited sk_prot by tcp_bpf_clone. This leads to issues like infinite recursion on close [1], because the child state is otherwise not set up for use with tcp_bpf_prot operations. Adjust the check in tcp_bpf_clone to detect all of tcp_bpf_prots variants. Note that it wouldn&#39;t be sufficient to check the socket state when overriding the sk_prot in tcp_bpf_update_proto in order to always use the TCP_BPF_BASE variant for listening sockets. Since commit b8b8315e39ff (&#34;bpf, sockmap: Remove unhash handler for BPF sockmap usage&#34;) it i…</p> https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-52986 https://vulnerability.circl.lu/vuln/wid-sec-w-2025-0649 <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Effekte zu erzielen.</p> <p>Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Effekte zu erzielen.</p> https://vulnerability.circl.lu/vuln/wid-sec-w-2025-0649