<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 09:06:14 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-09918</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-09918</link>
      <description>bdu:2025-09918</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-09918</guid>
    </item>
    <item>
      <title>BELL-CVE-2025-38154</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2025-38154</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2025-38154</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0698 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2025-avi-0698</link>
      <description>certfr-2025-avi-0698</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-0698</guid>
    </item>
    <item>
      <title>EUVD-2026-346940</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346940</link>
      <description>EUVD-2026-346940</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346940</guid>
    </item>
    <item>
      <title>fkie_cve-2025-38154</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-38154</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf, sockmap: Avoid using sk_socket after free when sending&lt;/p&gt;
&lt;p&gt;The sk-&amp;gt;sk_socket is not locked or referenced in backlog thread, and
during the call to skb_send_sock(), there is a race condition with
the release of sk_socket. All types of sockets(tcp/udp/unix/vsock)
will be affected.&lt;/p&gt;
&lt;p&gt;Race conditions:
&amp;#39;&amp;#39;&amp;#39;
CPU0                               CPU1&lt;/p&gt;
&lt;p&gt;backlog::skb_send_sock
  sendmsg_unlocked
    sock_sendmsg
      sock_sendmsg_nosec
                                   close(fd):
                                     ...
                                     ops-&amp;gt;release() -&amp;gt; sock_map_close()
                                     sk_socket-&amp;gt;ops = NULL
                                     free(socket)
      sock-&amp;gt;ops-&amp;gt;sendmsg
            ^
            panic here
&amp;#39;&amp;#39;&amp;#39;&lt;/p&gt;
&lt;p&gt;The ref of psock become 0 after sock_map_close() executed.
&amp;#39;&amp;#39;&amp;#39;
void sock_map_close()
{
    ...
    if (likely(psock)) {
    ...
    // !! here we remove psock and the ref of psock become 0
    sock_map_remove_links(sk, psock)
    psock = sk_psock_get(sk);
    if (unlikely(!psock))
        goto no_psock; &amp;lt;=== Control jumps here via goto
        ...
        cancel_delayed_work_sync(&amp;amp;psock-&amp;gt;work); &amp;lt;=== not executed
        sk_psock_put(sk, psock);
        ...
}
&amp;#39;&amp;#39;&amp;#39;&lt;/p&gt;
&lt;p&gt;Based on the fact that we already wait for the workqueue to finish in
sock_map_close() if psock is held, we simply increase the psock
reference count to avoid race conditions.&lt;/p&gt;
&lt;p&gt;With this patch, if t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf, sockmap: Avoid using sk_socket after free when sending&lt;/p&gt;
&lt;p&gt;The sk-&amp;gt;sk_socket is not locked or referenced in backlog thread, and
during the call to skb_send_sock(), there is a race condition with
the release of sk_socket. All types of sockets(tcp/udp/unix/vsock)
will be affected.&lt;/p&gt;
&lt;p&gt;Race conditions:
&amp;#39;&amp;#39;&amp;#39;
CPU0                               CPU1&lt;/p&gt;
&lt;p&gt;backlog::skb_send_sock
  sendmsg_unlocked
    sock_sendmsg
      sock_sendmsg_nosec
                                   close(fd):
                                     ...
                                     ops-&amp;gt;release() -&amp;gt; sock_map_close()
                                     sk_socket-&amp;gt;ops = NULL
                                     free(socket)
      sock-&amp;gt;ops-&amp;gt;sendmsg
            ^
            panic here
&amp;#39;&amp;#39;&amp;#39;&lt;/p&gt;
&lt;p&gt;The ref of psock become 0 after sock_map_close() executed.
&amp;#39;&amp;#39;&amp;#39;
void sock_map_close()
{
    ...
    if (likely(psock)) {
    ...
    // !! here we remove psock and the ref of psock become 0
    sock_map_remove_links(sk, psock)
    psock = sk_psock_get(sk);
    if (unlikely(!psock))
        goto no_psock; &amp;lt;=== Control jumps here via goto
        ...
        cancel_delayed_work_sync(&amp;amp;psock-&amp;gt;work); &amp;lt;=== not executed
        sk_psock_put(sk, psock);
        ...
}
&amp;#39;&amp;#39;&amp;#39;&lt;/p&gt;
&lt;p&gt;Based on the fact that we already wait for the workqueue to finish in
sock_map_close() if psock is held, we simply increase the psock
reference count to avoid race conditions.&lt;/p&gt;
&lt;p&gt;With this patch, if t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-38154</guid>
    </item>
    <item>
      <title>GHSA-vvj3-j4jg-68hm</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vvj3-j4jg-68hm</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf, sockmap: Avoid using sk_socket after free when sending&lt;/p&gt;
&lt;p&gt;The sk-&amp;gt;sk_socket is not locked or referenced in backlog thread, and
during the call to skb_send_sock(), there is a race condition with
the release of sk_socket. All types of sockets(tcp/udp/unix/vsock)
will be affected.&lt;/p&gt;
&lt;p&gt;Race conditions:
&amp;#39;&amp;#39;&amp;#39;
CPU0                               CPU1&lt;/p&gt;
&lt;p&gt;backlog::skb_send_sock
  sendmsg_unlocked
    sock_sendmsg
      sock_sendmsg_nosec
                                   close(fd):
                                     ...
                                     ops-&amp;gt;release() -&amp;gt; sock_map_close()
                                     sk_socket-&amp;gt;ops = NULL
                                     free(socket)
      sock-&amp;gt;ops-&amp;gt;sendmsg
            ^
            panic here
&amp;#39;&amp;#39;&amp;#39;&lt;/p&gt;
&lt;p&gt;The ref of psock become 0 after sock_map_close() executed.
&amp;#39;&amp;#39;&amp;#39;
void sock_map_close()
{
    ...
    if (likely(psock)) {
    ...
    // !! here we remove psock and the ref of psock become 0
    sock_map_remove_links(sk, psock)
    psock = sk_psock_get(sk);
    if (unlikely(!psock))
        goto no_psock; &amp;lt;=== Control jumps here via goto
        ...
        cancel_delayed_work_sync(&amp;amp;psock-&amp;gt;work); &amp;lt;=== not executed
        sk_psock_put(sk, psock);
        ...
}
&amp;#39;&amp;#39;&amp;#39;&lt;/p&gt;
&lt;p&gt;Based on the fact that we already wait for the workqueue to finish in
sock_map_close() if psock is held, we simply increase the psock
reference count to avoid race conditions.&lt;/p&gt;
&lt;p&gt;With this patch, if t…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf, sockmap: Avoid using sk_socket after free when sending&lt;/p&gt;
&lt;p&gt;The sk-&amp;gt;sk_socket is not locked or referenced in backlog thread, and
during the call to skb_send_sock(), there is a race condition with
the release of sk_socket. All types of sockets(tcp/udp/unix/vsock)
will be affected.&lt;/p&gt;
&lt;p&gt;Race conditions:
&amp;#39;&amp;#39;&amp;#39;
CPU0                               CPU1&lt;/p&gt;
&lt;p&gt;backlog::skb_send_sock
  sendmsg_unlocked
    sock_sendmsg
      sock_sendmsg_nosec
                                   close(fd):
                                     ...
                                     ops-&amp;gt;release() -&amp;gt; sock_map_close()
                                     sk_socket-&amp;gt;ops = NULL
                                     free(socket)
      sock-&amp;gt;ops-&amp;gt;sendmsg
            ^
            panic here
&amp;#39;&amp;#39;&amp;#39;&lt;/p&gt;
&lt;p&gt;The ref of psock become 0 after sock_map_close() executed.
&amp;#39;&amp;#39;&amp;#39;
void sock_map_close()
{
    ...
    if (likely(psock)) {
    ...
    // !! here we remove psock and the ref of psock become 0
    sock_map_remove_links(sk, psock)
    psock = sk_psock_get(sk);
    if (unlikely(!psock))
        goto no_psock; &amp;lt;=== Control jumps here via goto
        ...
        cancel_delayed_work_sync(&amp;amp;psock-&amp;gt;work); &amp;lt;=== not executed
        sk_psock_put(sk, psock);
        ...
}
&amp;#39;&amp;#39;&amp;#39;&lt;/p&gt;
&lt;p&gt;Based on the fact that we already wait for the workqueue to finish in
sock_map_close() if psock is held, we simply increase the psock
reference count to avoid race conditions.&lt;/p&gt;
&lt;p&gt;With this patch, if t…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vvj3-j4jg-68hm</guid>
    </item>
    <item>
      <title>OESA-2025-2120 — kernel security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2025-2120</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;gtp: Destroy device along with udp socket&amp;amp;apos;s netns dismantle.&lt;/p&gt;
&lt;p&gt;gtp_newlink() links the device to a list in dev_net(dev) instead of
src_net, where a udp tunnel socket is created.&lt;/p&gt;
&lt;p&gt;Even when src_net is removed, the device stays alive on dev_net(dev).
Then, removing src_net triggers the splat below. [0]&lt;/p&gt;
&lt;p&gt;In this example, gtp0 is created in ns2, and the udp socket is created
in ns1.&lt;/p&gt;
&lt;p&gt;ip netns add ns1
  ip netns add ns2
  ip -n ns1 link add netns ns2 name gtp0 type gtp role sgsn
  ip netns del ns1&lt;/p&gt;
&lt;p&gt;Let&amp;amp;apos;s link the device to the socket&amp;amp;apos;s netns instead.&lt;/p&gt;
&lt;p&gt;Now, gtp_net_exit_batch_rtnl() needs another netdev iteration to remove
all gtp devices in the netns.&lt;/p&gt;
&lt;p&gt;[0]:
ref_tracker: net notrefcnt@000000003d6e7d05 has 1/2 users at
     sk_alloc (./include/net/net_namespace.h:345 net/core/sock.c:2236)
     inet_create (net/ipv4/af_inet.c:326 net/ipv4/af_inet.c:252)
     __sock_create (net/socket.c:1558)
     udp_sock_create4 (net/ipv4/udp_tunnel_core.c:18)
     gtp_create_sock (./include/net/udp_tunnel.h:59 drivers/net/gtp.c:1423)
     gtp_create_sockets (drivers/net/gtp.c:1447)
     gtp_newlink (drivers/net/gtp.c:1507)
     rtnl_newlink (net/core/rtnetlink.c:3786 net/core/rtnetlink.c:3897 net/core/rtnetlink.c:4012)
     rtnetlink_rcv_msg (net/core/rtnetlink.c:6922)
     netlink_rcv_skb (net/netlink/af_netlink.c:2542)
     netlink_unicast…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:24.03-LTS: kernel&lt;/p&gt;
&lt;p&gt;The Linux Kernel, the operating system core itself.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;gtp: Destroy device along with udp socket&amp;amp;apos;s netns dismantle.&lt;/p&gt;
&lt;p&gt;gtp_newlink() links the device to a list in dev_net(dev) instead of
src_net, where a udp tunnel socket is created.&lt;/p&gt;
&lt;p&gt;Even when src_net is removed, the device stays alive on dev_net(dev).
Then, removing src_net triggers the splat below. [0]&lt;/p&gt;
&lt;p&gt;In this example, gtp0 is created in ns2, and the udp socket is created
in ns1.&lt;/p&gt;
&lt;p&gt;ip netns add ns1
  ip netns add ns2
  ip -n ns1 link add netns ns2 name gtp0 type gtp role sgsn
  ip netns del ns1&lt;/p&gt;
&lt;p&gt;Let&amp;amp;apos;s link the device to the socket&amp;amp;apos;s netns instead.&lt;/p&gt;
&lt;p&gt;Now, gtp_net_exit_batch_rtnl() needs another netdev iteration to remove
all gtp devices in the netns.&lt;/p&gt;
&lt;p&gt;[0]:
ref_tracker: net notrefcnt@000000003d6e7d05 has 1/2 users at
     sk_alloc (./include/net/net_namespace.h:345 net/core/sock.c:2236)
     inet_create (net/ipv4/af_inet.c:326 net/ipv4/af_inet.c:252)
     __sock_create (net/socket.c:1558)
     udp_sock_create4 (net/ipv4/udp_tunnel_core.c:18)
     gtp_create_sock (./include/net/udp_tunnel.h:59 drivers/net/gtp.c:1423)
     gtp_create_sockets (drivers/net/gtp.c:1447)
     gtp_newlink (drivers/net/gtp.c:1507)
     rtnl_newlink (net/core/rtnetlink.c:3786 net/core/rtnetlink.c:3897 net/core/rtnetlink.c:4012)
     rtnetlink_rcv_msg (net/core/rtnetlink.c:6922)
     netlink_rcv_skb (net/netlink/af_netlink.c:2542)
     netlink_unicast…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2025-2120</guid>
    </item>
    <item>
      <title>openSUSE-SU-2025:20081-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2025:20081-1</guid>
    </item>
    <item>
      <title>RHSA-2026:27731 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:27731</link>
      <description>&lt;p&gt;kernel: ceph: kernel: Ceph: exploit of hardcoded IVECs, in a misuse of AES, resulting in authentication bypass kernel: Linux kernel: Use-after-free in BPF sockmap can lead to denial of service and privilege escalation kernel: ipv6: use RCU in ip6_xmit() kernel: ipv6: use RCU in ip6_output() kernel: net: use dst_dev_rcu() in sk_setup_caps() kernel: Linux kernel: Denial of Service in libceph OSD client due to unreset sparse-read state kernel: can: isotp: fix tx.buf use-after-free in isotp_sendmsg() kernel: netfilter: ctnetlink: ensure safe access to master conntrack kernel: ipv6: rpl: reserve mac_len headroom when recompressed SRH grows kernel: RDMA/iwcm: Fix workqueue list corruption by removing work_list kernel: wifi: mac80211: remove station if connection prep fails kernel: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL kernel: Linux kernel: Use-After-Free in net/gro due to improper handling of zerocopy skbs kernel: net/sched: act_pedit: extend the writable skb range per key&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: ceph: kernel: Ceph: exploit of hardcoded IVECs, in a misuse of AES, resulting in authentication bypass kernel: Linux kernel: Use-after-free in BPF sockmap can lead to denial of service and privilege escalation kernel: ipv6: use RCU in ip6_xmit() kernel: ipv6: use RCU in ip6_output() kernel: net: use dst_dev_rcu() in sk_setup_caps() kernel: Linux kernel: Denial of Service in libceph OSD client due to unreset sparse-read state kernel: can: isotp: fix tx.buf use-after-free in isotp_sendmsg() kernel: netfilter: ctnetlink: ensure safe access to master conntrack kernel: ipv6: rpl: reserve mac_len headroom when recompressed SRH grows kernel: RDMA/iwcm: Fix workqueue list corruption by removing work_list kernel: wifi: mac80211: remove station if connection prep fails kernel: sctp: revalidate list cursor after sctp_sendmsg_to_asoc() in SCTP_SENDALL kernel: Linux kernel: Use-After-Free in net/gro due to improper handling of zerocopy skbs kernel: net/sched: act_pedit: extend the writable skb range per key&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:27731</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:02853-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:02853-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2025:02853-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38154</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38154</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Avoid using sk_socket after free when sending The sk-&amp;gt;sk_socket is not locked or referenced in backlog thread, and during the call to skb_send_sock(), there is a race condition with the release of sk_socket. All types of sockets(tcp/udp/unix/vsock) will be affected. Race conditions: &amp;#39;&amp;#39;&amp;#39; CPU0                               CPU1 backlog::skb_send_sock   sendmsg_unlocked     sock_sendmsg       sock_sendmsg_nosec                                    close(fd):                                      ...                                      ops-&amp;gt;release() -&amp;gt; sock_map_close()                                      sk_socket-&amp;gt;ops = NULL                                      free(socket)       sock-&amp;gt;ops-&amp;gt;sendmsg             ^             panic here &amp;#39;&amp;#39;&amp;#39; The ref of psock become 0 after sock_map_close() executed. &amp;#39;&amp;#39;&amp;#39; void sock_map_close() {     ...     if (likely(psock)) {     ...     // !! here we remove psock and the ref of psock become 0     sock_map_remove_links(sk, psock)     psock = sk_psock_get(sk);     if (unlikely(!psock))         goto no_psock; &amp;lt;=== Control jumps here via goto         ...         cancel_delayed_work_sync(&amp;amp;psock-&amp;gt;work); &amp;lt;=== not executed         sk_psock_put(sk, psock);         ... } &amp;#39;&amp;#39;&amp;#39; Based on the fact that we already wait for the workqueue to finish in sock_map_close() if psock is held, we simply increase the psock reference count to avoid race conditions. With this patch, if the back…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Avoid using sk_socket after free when sending The sk-&amp;gt;sk_socket is not locked or referenced in backlog thread, and during the call to skb_send_sock(), there is a race condition with the release of sk_socket. All types of sockets(tcp/udp/unix/vsock) will be affected. Race conditions: &amp;#39;&amp;#39;&amp;#39; CPU0                               CPU1 backlog::skb_send_sock   sendmsg_unlocked     sock_sendmsg       sock_sendmsg_nosec                                    close(fd):                                      ...                                      ops-&amp;gt;release() -&amp;gt; sock_map_close()                                      sk_socket-&amp;gt;ops = NULL                                      free(socket)       sock-&amp;gt;ops-&amp;gt;sendmsg             ^             panic here &amp;#39;&amp;#39;&amp;#39; The ref of psock become 0 after sock_map_close() executed. &amp;#39;&amp;#39;&amp;#39; void sock_map_close() {     ...     if (likely(psock)) {     ...     // !! here we remove psock and the ref of psock become 0     sock_map_remove_links(sk, psock)     psock = sk_psock_get(sk);     if (unlikely(!psock))         goto no_psock; &amp;lt;=== Control jumps here via goto         ...         cancel_delayed_work_sync(&amp;amp;psock-&amp;gt;work); &amp;lt;=== not executed         sk_psock_put(sk, psock);         ... } &amp;#39;&amp;#39;&amp;#39; Based on the fact that we already wait for the workqueue to finish in sock_map_close() if psock is held, we simply increase the psock reference count to avoid race conditions. With this patch, if the back…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-38154</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-1452 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1452</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere, nicht spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere, nicht spezifizierte Auswirkungen zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-1452</guid>
    </item>
  </channel>
</rss>
