<?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://vulnerability.circl.lu</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>Thu, 01 Oct 2026 20:42:25 +0000</lastBuildDate>
    <item>
      <title>CERTFR-2025-AVI-0895 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-0895</link>
      <description>CERTFR-2025-AVI-0895</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-0895</guid>
    </item>
    <item>
      <title>bdu:2025-16298</title>
      <link>https://vulnerability.circl.lu/vuln/bdu:2025-16298</link>
      <description>bdu:2025-16298</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bdu:2025-16298</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53489</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2023-53489</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bell-cve-2023-53489</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53489</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2023-53489</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp.&lt;/p&gt;
&lt;p&gt;syzkaller reported [0] memory leaks of an UDP socket and ZEROCOPY
skbs.  We can reproduce the problem with these sequences:&lt;/p&gt;
&lt;p&gt;sk = socket(AF_INET, SOCK_DGRAM, 0)
  sk.setsockopt(SOL_SOCKET, SO_TIMESTAMPING, SOF_TIMESTAMPING_TX_SOFTWARE)
  sk.setsockopt(SOL_SOCKET, SO_ZEROCOPY, 1)
  sk.sendto(b&amp;#39;&amp;#39;, MSG_ZEROCOPY, (&amp;#39;127.0.0.1&amp;#39;, 53))
  sk.close()&lt;/p&gt;
&lt;p&gt;sendmsg() calls msg_zerocopy_alloc(), which allocates a skb, sets
skb-&amp;gt;cb-&amp;gt;ubuf.refcnt to 1, and calls sock_hold().  Here, struct
ubuf_info_msgzc indirectly holds a refcnt of the socket.  When the
skb is sent, __skb_tstamp_tx() clones it and puts the clone into
the socket&amp;#39;s error queue with the TX timestamp.&lt;/p&gt;
&lt;p&gt;When the original skb is received locally, skb_copy_ubufs() calls
skb_unclone(), and pskb_expand_head() increments skb-&amp;gt;cb-&amp;gt;ubuf.refcnt.
This additional count is decremented while freeing the skb, but struct
ubuf_info_msgzc still has a refcnt, so __msg_zerocopy_callback() is
not called.&lt;/p&gt;
&lt;p&gt;The last refcnt is not released unless we retrieve the TX timestamped
skb by recvmsg().  Since we clear the error queue in inet_sock_destruct()
after the socket&amp;#39;s refcnt reaches 0, there is a circular dependency.
If we close() the socket holding such skbs, we never call sock_put()
and leak the count, sk, and skb.&lt;/p&gt;
&lt;p&gt;TCP has the same problem, and commit e0c8bccd40fc (&amp;#34;net: stream:
purge sk_error_queue in sk_stream_kil…&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;tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp.&lt;/p&gt;
&lt;p&gt;syzkaller reported [0] memory leaks of an UDP socket and ZEROCOPY
skbs.  We can reproduce the problem with these sequences:&lt;/p&gt;
&lt;p&gt;sk = socket(AF_INET, SOCK_DGRAM, 0)
  sk.setsockopt(SOL_SOCKET, SO_TIMESTAMPING, SOF_TIMESTAMPING_TX_SOFTWARE)
  sk.setsockopt(SOL_SOCKET, SO_ZEROCOPY, 1)
  sk.sendto(b&amp;#39;&amp;#39;, MSG_ZEROCOPY, (&amp;#39;127.0.0.1&amp;#39;, 53))
  sk.close()&lt;/p&gt;
&lt;p&gt;sendmsg() calls msg_zerocopy_alloc(), which allocates a skb, sets
skb-&amp;gt;cb-&amp;gt;ubuf.refcnt to 1, and calls sock_hold().  Here, struct
ubuf_info_msgzc indirectly holds a refcnt of the socket.  When the
skb is sent, __skb_tstamp_tx() clones it and puts the clone into
the socket&amp;#39;s error queue with the TX timestamp.&lt;/p&gt;
&lt;p&gt;When the original skb is received locally, skb_copy_ubufs() calls
skb_unclone(), and pskb_expand_head() increments skb-&amp;gt;cb-&amp;gt;ubuf.refcnt.
This additional count is decremented while freeing the skb, but struct
ubuf_info_msgzc still has a refcnt, so __msg_zerocopy_callback() is
not called.&lt;/p&gt;
&lt;p&gt;The last refcnt is not released unless we retrieve the TX timestamped
skb by recvmsg().  Since we clear the error queue in inet_sock_destruct()
after the socket&amp;#39;s refcnt reaches 0, there is a circular dependency.
If we close() the socket holding such skbs, we never call sock_put()
and leak the count, sk, and skb.&lt;/p&gt;
&lt;p&gt;TCP has the same problem, and commit e0c8bccd40fc (&amp;#34;net: stream:
purge sk_error_queue in sk_stream_kil…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2023-53489</guid>
    </item>
    <item>
      <title>GHSA-5wf2-hxf9-8hxr</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-5wf2-hxf9-8hxr</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp.&lt;/p&gt;
&lt;p&gt;syzkaller reported [0] memory leaks of an UDP socket and ZEROCOPY
skbs.  We can reproduce the problem with these sequences:&lt;/p&gt;
&lt;p&gt;sk = socket(AF_INET, SOCK_DGRAM, 0)
  sk.setsockopt(SOL_SOCKET, SO_TIMESTAMPING, SOF_TIMESTAMPING_TX_SOFTWARE)
  sk.setsockopt(SOL_SOCKET, SO_ZEROCOPY, 1)
  sk.sendto(b&amp;#39;&amp;#39;, MSG_ZEROCOPY, (&amp;#39;127.0.0.1&amp;#39;, 53))
  sk.close()&lt;/p&gt;
&lt;p&gt;sendmsg() calls msg_zerocopy_alloc(), which allocates a skb, sets
skb-&amp;gt;cb-&amp;gt;ubuf.refcnt to 1, and calls sock_hold().  Here, struct
ubuf_info_msgzc indirectly holds a refcnt of the socket.  When the
skb is sent, __skb_tstamp_tx() clones it and puts the clone into
the socket&amp;#39;s error queue with the TX timestamp.&lt;/p&gt;
&lt;p&gt;When the original skb is received locally, skb_copy_ubufs() calls
skb_unclone(), and pskb_expand_head() increments skb-&amp;gt;cb-&amp;gt;ubuf.refcnt.
This additional count is decremented while freeing the skb, but struct
ubuf_info_msgzc still has a refcnt, so __msg_zerocopy_callback() is
not called.&lt;/p&gt;
&lt;p&gt;The last refcnt is not released unless we retrieve the TX timestamped
skb by recvmsg().  Since we clear the error queue in inet_sock_destruct()
after the socket&amp;#39;s refcnt reaches 0, there is a circular dependency.
If we close() the socket holding such skbs, we never call sock_put()
and leak the count, sk, and skb.&lt;/p&gt;
&lt;p&gt;TCP has the same problem, and commit e0c8bccd40fc (&amp;#34;net: stream:
purge sk_error_queue in sk_stream_kil…&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;tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp.&lt;/p&gt;
&lt;p&gt;syzkaller reported [0] memory leaks of an UDP socket and ZEROCOPY
skbs.  We can reproduce the problem with these sequences:&lt;/p&gt;
&lt;p&gt;sk = socket(AF_INET, SOCK_DGRAM, 0)
  sk.setsockopt(SOL_SOCKET, SO_TIMESTAMPING, SOF_TIMESTAMPING_TX_SOFTWARE)
  sk.setsockopt(SOL_SOCKET, SO_ZEROCOPY, 1)
  sk.sendto(b&amp;#39;&amp;#39;, MSG_ZEROCOPY, (&amp;#39;127.0.0.1&amp;#39;, 53))
  sk.close()&lt;/p&gt;
&lt;p&gt;sendmsg() calls msg_zerocopy_alloc(), which allocates a skb, sets
skb-&amp;gt;cb-&amp;gt;ubuf.refcnt to 1, and calls sock_hold().  Here, struct
ubuf_info_msgzc indirectly holds a refcnt of the socket.  When the
skb is sent, __skb_tstamp_tx() clones it and puts the clone into
the socket&amp;#39;s error queue with the TX timestamp.&lt;/p&gt;
&lt;p&gt;When the original skb is received locally, skb_copy_ubufs() calls
skb_unclone(), and pskb_expand_head() increments skb-&amp;gt;cb-&amp;gt;ubuf.refcnt.
This additional count is decremented while freeing the skb, but struct
ubuf_info_msgzc still has a refcnt, so __msg_zerocopy_callback() is
not called.&lt;/p&gt;
&lt;p&gt;The last refcnt is not released unless we retrieve the TX timestamped
skb by recvmsg().  Since we clear the error queue in inet_sock_destruct()
after the socket&amp;#39;s refcnt reaches 0, there is a circular dependency.
If we close() the socket holding such skbs, we never call sock_put()
and leak the count, sk, and skb.&lt;/p&gt;
&lt;p&gt;TCP has the same problem, and commit e0c8bccd40fc (&amp;#34;net: stream:
purge sk_error_queue in sk_stream_kil…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-5wf2-hxf9-8hxr</guid>
    </item>
    <item>
      <title>RHSA-2023:6583 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2023:6583</link>
      <description>&lt;p&gt;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&amp;#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…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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&amp;#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…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2023:6583</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:03615-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2025:03615-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://vulnerability.circl.lu/vuln/suse-su-2025:03615-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53489</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53489</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp. syzkaller reported [0] memory leaks of an UDP socket and ZEROCOPY skbs.  We can reproduce the problem with these sequences:   sk = socket(AF_INET, SOCK_DGRAM, 0)   sk.setsockopt(SOL_SOCKET, SO_TIMESTAMPING, SOF_TIMESTAMPING_TX_SOFTWARE)   sk.setsockopt(SOL_SOCKET, SO_ZEROCOPY, 1)   sk.sendto(b&amp;#39;&amp;#39;, MSG_ZEROCOPY, (&amp;#39;127.0.0.1&amp;#39;, 53))   sk.close() sendmsg() calls msg_zerocopy_alloc(), which allocates a skb, sets skb-&amp;gt;cb-&amp;gt;ubuf.refcnt to 1, and calls sock_hold().  Here, struct ubuf_info_msgzc indirectly holds a refcnt of the socket.  When the skb is sent, __skb_tstamp_tx() clones it and puts the clone into the socket&amp;#39;s error queue with the TX timestamp. When the original skb is received locally, skb_copy_ubufs() calls skb_unclone(), and pskb_expand_head() increments skb-&amp;gt;cb-&amp;gt;ubuf.refcnt. This additional count is decremented while freeing the skb, but struct ubuf_info_msgzc still has a refcnt, so __msg_zerocopy_callback() is not called. The last refcnt is not released unless we retrieve the TX timestamped skb by recvmsg().  Since we clear the error queue in inet_sock_destruct() after the socket&amp;#39;s refcnt reaches 0, there is a circular dependency. If we close() the socket holding such skbs, we never call sock_put() and leak the count, sk, and skb. TCP has the same problem, and commit e0c8bccd40fc (&amp;#34;net: stream: purge sk_error_queue in sk_stream_kill_queue…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 155 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp. syzkaller reported [0] memory leaks of an UDP socket and ZEROCOPY skbs.  We can reproduce the problem with these sequences:   sk = socket(AF_INET, SOCK_DGRAM, 0)   sk.setsockopt(SOL_SOCKET, SO_TIMESTAMPING, SOF_TIMESTAMPING_TX_SOFTWARE)   sk.setsockopt(SOL_SOCKET, SO_ZEROCOPY, 1)   sk.sendto(b&amp;#39;&amp;#39;, MSG_ZEROCOPY, (&amp;#39;127.0.0.1&amp;#39;, 53))   sk.close() sendmsg() calls msg_zerocopy_alloc(), which allocates a skb, sets skb-&amp;gt;cb-&amp;gt;ubuf.refcnt to 1, and calls sock_hold().  Here, struct ubuf_info_msgzc indirectly holds a refcnt of the socket.  When the skb is sent, __skb_tstamp_tx() clones it and puts the clone into the socket&amp;#39;s error queue with the TX timestamp. When the original skb is received locally, skb_copy_ubufs() calls skb_unclone(), and pskb_expand_head() increments skb-&amp;gt;cb-&amp;gt;ubuf.refcnt. This additional count is decremented while freeing the skb, but struct ubuf_info_msgzc still has a refcnt, so __msg_zerocopy_callback() is not called. The last refcnt is not released unless we retrieve the TX timestamped skb by recvmsg().  Since we clear the error queue in inet_sock_destruct() after the socket&amp;#39;s refcnt reaches 0, there is a circular dependency. If we close() the socket holding such skbs, we never call sock_put() and leak the count, sk, and skb. TCP has the same problem, and commit e0c8bccd40fc (&amp;#34;net: stream: purge sk_error_queue in sk_stream_kill_queue…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53489</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2187 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2187</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und um nicht nähere beschriebene Effekte zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2025-2187</guid>
    </item>
  </channel>
</rss>
