<?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>Mon, 28 Sep 2026 17:07:42 +0000</lastBuildDate>
    <item>
      <title>CERTFR-2025-AVI-1047 — 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-1047</link>
      <description>CERTFR-2025-AVI-1047</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/CERTFR-2025-AVI-1047</guid>
    </item>
    <item>
      <title>bdu:2025-12908</title>
      <link>https://vulnerability.circl.lu/vuln/bdu:2025-12908</link>
      <description>bdu:2025-12908</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/bdu:2025-12908</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-53517</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2023-53517</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-53517</guid>
    </item>
    <item>
      <title>fkie_cve-2023-53517</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2023-53517</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tipc: do not update mtu if msg_max is too small in mtu negotiation&lt;/p&gt;
&lt;p&gt;When doing link mtu negotiation, a malicious peer may send Activate msg
with a very small mtu, e.g. 4 in Shuang&amp;#39;s testing, without checking for
the minimum mtu, l-&amp;gt;mtu will be set to 4 in tipc_link_proto_rcv(), then
n-&amp;gt;links[bearer_id].mtu is set to 4294967228, which is a overflow of
&amp;#39;4 - INT_H_SIZE - EMSG_OVERHEAD&amp;#39; in tipc_link_mss().&lt;/p&gt;
&lt;p&gt;With tipc_link.mtu = 4, tipc_link_xmit() kept printing the warning:&lt;/p&gt;
&lt;p&gt;tipc: Too large msg, purging xmit list 1 5 0 40 4!
 tipc: Too large msg, purging xmit list 1 15 0 60 4!&lt;/p&gt;
&lt;p&gt;And with tipc_link_entry.mtu 4294967228, a huge skb was allocated in
named_distribute(), and when purging it in tipc_link_xmit(), a crash
was even caused:&lt;/p&gt;
&lt;p&gt;general protection fault, probably for non-canonical address 0x2100001011000dd: 0000 [#1] PREEMPT SMP PTI
  CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 6.3.0.neta #19
  RIP: 0010:kfree_skb_list_reason+0x7e/0x1f0
  Call Trace:
   &amp;lt;IRQ&amp;gt;
   skb_release_data+0xf9/0x1d0
   kfree_skb_reason+0x40/0x100
   tipc_link_xmit+0x57a/0x740 [tipc]
   tipc_node_xmit+0x16c/0x5c0 [tipc]
   tipc_named_node_up+0x27f/0x2c0 [tipc]
   tipc_node_write_unlock+0x149/0x170 [tipc]
   tipc_rcv+0x608/0x740 [tipc]
   tipc_udp_recv+0xdc/0x1f0 [tipc]
   udp_queue_rcv_one_skb+0x33e/0x620
   udp_unicast_rcv_skb.isra.72+0x75/0x90
   __udp4_lib_rcv+0x56d/0xc20
   ip_protocol_deliver_rcu+0x100/0x2d0&lt;/p&gt;
&lt;p&gt;This pa…&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;tipc: do not update mtu if msg_max is too small in mtu negotiation&lt;/p&gt;
&lt;p&gt;When doing link mtu negotiation, a malicious peer may send Activate msg
with a very small mtu, e.g. 4 in Shuang&amp;#39;s testing, without checking for
the minimum mtu, l-&amp;gt;mtu will be set to 4 in tipc_link_proto_rcv(), then
n-&amp;gt;links[bearer_id].mtu is set to 4294967228, which is a overflow of
&amp;#39;4 - INT_H_SIZE - EMSG_OVERHEAD&amp;#39; in tipc_link_mss().&lt;/p&gt;
&lt;p&gt;With tipc_link.mtu = 4, tipc_link_xmit() kept printing the warning:&lt;/p&gt;
&lt;p&gt;tipc: Too large msg, purging xmit list 1 5 0 40 4!
 tipc: Too large msg, purging xmit list 1 15 0 60 4!&lt;/p&gt;
&lt;p&gt;And with tipc_link_entry.mtu 4294967228, a huge skb was allocated in
named_distribute(), and when purging it in tipc_link_xmit(), a crash
was even caused:&lt;/p&gt;
&lt;p&gt;general protection fault, probably for non-canonical address 0x2100001011000dd: 0000 [#1] PREEMPT SMP PTI
  CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 6.3.0.neta #19
  RIP: 0010:kfree_skb_list_reason+0x7e/0x1f0
  Call Trace:
   &amp;lt;IRQ&amp;gt;
   skb_release_data+0xf9/0x1d0
   kfree_skb_reason+0x40/0x100
   tipc_link_xmit+0x57a/0x740 [tipc]
   tipc_node_xmit+0x16c/0x5c0 [tipc]
   tipc_named_node_up+0x27f/0x2c0 [tipc]
   tipc_node_write_unlock+0x149/0x170 [tipc]
   tipc_rcv+0x608/0x740 [tipc]
   tipc_udp_recv+0xdc/0x1f0 [tipc]
   udp_queue_rcv_one_skb+0x33e/0x620
   udp_unicast_rcv_skb.isra.72+0x75/0x90
   __udp4_lib_rcv+0x56d/0xc20
   ip_protocol_deliver_rcu+0x100/0x2d0&lt;/p&gt;
&lt;p&gt;This pa…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2023-53517</guid>
    </item>
    <item>
      <title>GHSA-hwgx-c53p-8gmw</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-hwgx-c53p-8gmw</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tipc: do not update mtu if msg_max is too small in mtu negotiation&lt;/p&gt;
&lt;p&gt;When doing link mtu negotiation, a malicious peer may send Activate msg
with a very small mtu, e.g. 4 in Shuang&amp;#39;s testing, without checking for
the minimum mtu, l-&amp;gt;mtu will be set to 4 in tipc_link_proto_rcv(), then
n-&amp;gt;links[bearer_id].mtu is set to 4294967228, which is a overflow of
&amp;#39;4 - INT_H_SIZE - EMSG_OVERHEAD&amp;#39; in tipc_link_mss().&lt;/p&gt;
&lt;p&gt;With tipc_link.mtu = 4, tipc_link_xmit() kept printing the warning:&lt;/p&gt;
&lt;p&gt;tipc: Too large msg, purging xmit list 1 5 0 40 4!
 tipc: Too large msg, purging xmit list 1 15 0 60 4!&lt;/p&gt;
&lt;p&gt;And with tipc_link_entry.mtu 4294967228, a huge skb was allocated in
named_distribute(), and when purging it in tipc_link_xmit(), a crash
was even caused:&lt;/p&gt;
&lt;p&gt;general protection fault, probably for non-canonical address 0x2100001011000dd: 0000 [#1] PREEMPT SMP PTI
  CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 6.3.0.neta #19
  RIP: 0010:kfree_skb_list_reason+0x7e/0x1f0
  Call Trace:
   &amp;lt;IRQ&amp;gt;
   skb_release_data+0xf9/0x1d0
   kfree_skb_reason+0x40/0x100
   tipc_link_xmit+0x57a/0x740 [tipc]
   tipc_node_xmit+0x16c/0x5c0 [tipc]
   tipc_named_node_up+0x27f/0x2c0 [tipc]
   tipc_node_write_unlock+0x149/0x170 [tipc]
   tipc_rcv+0x608/0x740 [tipc]
   tipc_udp_recv+0xdc/0x1f0 [tipc]
   udp_queue_rcv_one_skb+0x33e/0x620
   udp_unicast_rcv_skb.isra.72+0x75/0x90
   __udp4_lib_rcv+0x56d/0xc20
   ip_protocol_deliver_rcu+0x100/0x2d0&lt;/p&gt;
&lt;p&gt;This pa…&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;tipc: do not update mtu if msg_max is too small in mtu negotiation&lt;/p&gt;
&lt;p&gt;When doing link mtu negotiation, a malicious peer may send Activate msg
with a very small mtu, e.g. 4 in Shuang&amp;#39;s testing, without checking for
the minimum mtu, l-&amp;gt;mtu will be set to 4 in tipc_link_proto_rcv(), then
n-&amp;gt;links[bearer_id].mtu is set to 4294967228, which is a overflow of
&amp;#39;4 - INT_H_SIZE - EMSG_OVERHEAD&amp;#39; in tipc_link_mss().&lt;/p&gt;
&lt;p&gt;With tipc_link.mtu = 4, tipc_link_xmit() kept printing the warning:&lt;/p&gt;
&lt;p&gt;tipc: Too large msg, purging xmit list 1 5 0 40 4!
 tipc: Too large msg, purging xmit list 1 15 0 60 4!&lt;/p&gt;
&lt;p&gt;And with tipc_link_entry.mtu 4294967228, a huge skb was allocated in
named_distribute(), and when purging it in tipc_link_xmit(), a crash
was even caused:&lt;/p&gt;
&lt;p&gt;general protection fault, probably for non-canonical address 0x2100001011000dd: 0000 [#1] PREEMPT SMP PTI
  CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 6.3.0.neta #19
  RIP: 0010:kfree_skb_list_reason+0x7e/0x1f0
  Call Trace:
   &amp;lt;IRQ&amp;gt;
   skb_release_data+0xf9/0x1d0
   kfree_skb_reason+0x40/0x100
   tipc_link_xmit+0x57a/0x740 [tipc]
   tipc_node_xmit+0x16c/0x5c0 [tipc]
   tipc_named_node_up+0x27f/0x2c0 [tipc]
   tipc_node_write_unlock+0x149/0x170 [tipc]
   tipc_rcv+0x608/0x740 [tipc]
   tipc_udp_recv+0xdc/0x1f0 [tipc]
   udp_queue_rcv_one_skb+0x33e/0x620
   udp_unicast_rcv_skb.isra.72+0x75/0x90
   __udp4_lib_rcv+0x56d/0xc20
   ip_protocol_deliver_rcu+0x100/0x2d0&lt;/p&gt;
&lt;p&gt;This pa…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-hwgx-c53p-8gmw</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:4189-1 — Security update for the Linux Kernel</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2025:4189-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:4189-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-53517</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53517</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 161 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tipc: do not update mtu if msg_max is too small in mtu negotiation When doing link mtu negotiation, a malicious peer may send Activate msg with a very small mtu, e.g. 4 in Shuang&amp;#39;s testing, without checking for the minimum mtu, l-&amp;gt;mtu will be set to 4 in tipc_link_proto_rcv(), then n-&amp;gt;links[bearer_id].mtu is set to 4294967228, which is a overflow of &amp;#39;4 - INT_H_SIZE - EMSG_OVERHEAD&amp;#39; in tipc_link_mss(). With tipc_link.mtu = 4, tipc_link_xmit() kept printing the warning:  tipc: Too large msg, purging xmit list 1 5 0 40 4!  tipc: Too large msg, purging xmit list 1 15 0 60 4! And with tipc_link_entry.mtu 4294967228, a huge skb was allocated in named_distribute(), and when purging it in tipc_link_xmit(), a crash was even caused:   general protection fault, probably for non-canonical address 0x2100001011000dd: 0000 [#1] PREEMPT SMP PTI   CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 6.3.0.neta #19   RIP: 0010:kfree_skb_list_reason+0x7e/0x1f0   Call Trace:    &amp;lt;IRQ&amp;gt;    skb_release_data+0xf9/0x1d0    kfree_skb_reason+0x40/0x100    tipc_link_xmit+0x57a/0x740 [tipc]    tipc_node_xmit+0x16c/0x5c0 [tipc]    tipc_named_node_up+0x27f/0x2c0 [tipc]    tipc_node_write_unlock+0x149/0x170 [tipc]    tipc_rcv+0x608/0x740 [tipc]    tipc_udp_recv+0xdc/0x1f0 [tipc]    udp_queue_rcv_one_skb+0x33e/0x620    udp_unicast_rcv_skb.isra.72+0x75/0x90    __udp4_lib_rcv+0x56d/0xc20    ip_protocol_deliver_rcu+0x100/0x2d0 This patch fix…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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 and 161 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: tipc: do not update mtu if msg_max is too small in mtu negotiation When doing link mtu negotiation, a malicious peer may send Activate msg with a very small mtu, e.g. 4 in Shuang&amp;#39;s testing, without checking for the minimum mtu, l-&amp;gt;mtu will be set to 4 in tipc_link_proto_rcv(), then n-&amp;gt;links[bearer_id].mtu is set to 4294967228, which is a overflow of &amp;#39;4 - INT_H_SIZE - EMSG_OVERHEAD&amp;#39; in tipc_link_mss(). With tipc_link.mtu = 4, tipc_link_xmit() kept printing the warning:  tipc: Too large msg, purging xmit list 1 5 0 40 4!  tipc: Too large msg, purging xmit list 1 15 0 60 4! And with tipc_link_entry.mtu 4294967228, a huge skb was allocated in named_distribute(), and when purging it in tipc_link_xmit(), a crash was even caused:   general protection fault, probably for non-canonical address 0x2100001011000dd: 0000 [#1] PREEMPT SMP PTI   CPU: 0 PID: 0 Comm: swapper/0 Kdump: loaded Not tainted 6.3.0.neta #19   RIP: 0010:kfree_skb_list_reason+0x7e/0x1f0   Call Trace:    &amp;lt;IRQ&amp;gt;    skb_release_data+0xf9/0x1d0    kfree_skb_reason+0x40/0x100    tipc_link_xmit+0x57a/0x740 [tipc]    tipc_node_xmit+0x16c/0x5c0 [tipc]    tipc_named_node_up+0x27f/0x2c0 [tipc]    tipc_node_write_unlock+0x149/0x170 [tipc]    tipc_rcv+0x608/0x740 [tipc]    tipc_udp_recv+0xdc/0x1f0 [tipc]    udp_queue_rcv_one_skb+0x33e/0x620    udp_unicast_rcv_skb.isra.72+0x75/0x90    __udp4_lib_rcv+0x56d/0xc20    ip_protocol_deliver_rcu+0x100/0x2d0 This patch fix…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2023-53517</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>
