<?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 16:08:24 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-97958</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-97958</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/sched: cls_api: Don&amp;#39;t replay RTM_GETCHAIN in tc_ctl_chain().&lt;/p&gt;
&lt;p&gt;If a netlink socket sends RTM_GETCHAIN requests repeatedly
without recv()ing the responses, tc_ctl_chain() hogs CPU and
triggers Hung Task splat. [0]&lt;/p&gt;
&lt;p&gt;As caught in the stack trace, netlink_attachskb() could confuse
tc_ctl_chain() by returning -EAGAIN when the userspace netlink
socket&amp;#39;s receive buffer is full.&lt;/p&gt;
&lt;p&gt;The replay: label exists since commit 32a4f5ecd738 (&amp;#34;net: sched:
introduce chain object to uapi&amp;#34;) but was not used initially.&lt;/p&gt;
&lt;p&gt;Since commit 9f407f1768d3 (&amp;#34;net: sched: introduce chain templates&amp;#34;),
the label is needed for RTM_NEWCHAIN because tcf_proto_lookup_ops()
may release RTNL to call request_module().&lt;/p&gt;
&lt;p&gt;However, the replay logic is unnecessary for RTM_GETCHAIN.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s apply the replay logic only for RTM_NEWCHAIN.&lt;/p&gt;
&lt;p&gt;[0]:
INFO: task repro:1018 is blocked on a mutex likely owned by task repro:1022.
task:repro           state:R  running task     stack:14096 pid:1022  tgid:1014  ppid:961    task_flags:0x400040 flags:0x00080000
Call Trace:
 &amp;lt;TASK&amp;gt;
 ? clockevents_program_event (kernel/time/clockevents.c:372)
 ? pskb_expand_head (net/core/skbuff.c:615)
 ? skb_release_data (net/core/skbuff.c:1122)
 ? netlink_attachskb (./include/linux/skbuff.h:1323 ./include/linux/skbuff.h:1332 net/netlink/af_netlink.c:1232)
 ? __netlink_lookup (./include/linux/rcupdate.h:882 ./include/linux/rhashtable.h:711 net/netlink/af_netlink.c:499)
 ? tc_chain_notify (ne…&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;net/sched: cls_api: Don&amp;#39;t replay RTM_GETCHAIN in tc_ctl_chain().&lt;/p&gt;
&lt;p&gt;If a netlink socket sends RTM_GETCHAIN requests repeatedly
without recv()ing the responses, tc_ctl_chain() hogs CPU and
triggers Hung Task splat. [0]&lt;/p&gt;
&lt;p&gt;As caught in the stack trace, netlink_attachskb() could confuse
tc_ctl_chain() by returning -EAGAIN when the userspace netlink
socket&amp;#39;s receive buffer is full.&lt;/p&gt;
&lt;p&gt;The replay: label exists since commit 32a4f5ecd738 (&amp;#34;net: sched:
introduce chain object to uapi&amp;#34;) but was not used initially.&lt;/p&gt;
&lt;p&gt;Since commit 9f407f1768d3 (&amp;#34;net: sched: introduce chain templates&amp;#34;),
the label is needed for RTM_NEWCHAIN because tcf_proto_lookup_ops()
may release RTNL to call request_module().&lt;/p&gt;
&lt;p&gt;However, the replay logic is unnecessary for RTM_GETCHAIN.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s apply the replay logic only for RTM_NEWCHAIN.&lt;/p&gt;
&lt;p&gt;[0]:
INFO: task repro:1018 is blocked on a mutex likely owned by task repro:1022.
task:repro           state:R  running task     stack:14096 pid:1022  tgid:1014  ppid:961    task_flags:0x400040 flags:0x00080000
Call Trace:
 &amp;lt;TASK&amp;gt;
 ? clockevents_program_event (kernel/time/clockevents.c:372)
 ? pskb_expand_head (net/core/skbuff.c:615)
 ? skb_release_data (net/core/skbuff.c:1122)
 ? netlink_attachskb (./include/linux/skbuff.h:1323 ./include/linux/skbuff.h:1332 net/netlink/af_netlink.c:1232)
 ? __netlink_lookup (./include/linux/rcupdate.h:882 ./include/linux/rhashtable.h:711 net/netlink/af_netlink.c:499)
 ? tc_chain_notify (ne…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-97958</guid>
    </item>
    <item>
      <title>GHSA-wrg6-48wc-j3w4</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-wrg6-48wc-j3w4</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;net/sched: cls_api: Don&amp;#39;t replay RTM_GETCHAIN in tc_ctl_chain().&lt;/p&gt;
&lt;p&gt;If a netlink socket sends RTM_GETCHAIN requests repeatedly
without recv()ing the responses, tc_ctl_chain() hogs CPU and
triggers Hung Task splat. [0]&lt;/p&gt;
&lt;p&gt;As caught in the stack trace, netlink_attachskb() could confuse
tc_ctl_chain() by returning -EAGAIN when the userspace netlink
socket&amp;#39;s receive buffer is full.&lt;/p&gt;
&lt;p&gt;The replay: label exists since commit 32a4f5ecd738 (&amp;#34;net: sched:
introduce chain object to uapi&amp;#34;) but was not used initially.&lt;/p&gt;
&lt;p&gt;Since commit 9f407f1768d3 (&amp;#34;net: sched: introduce chain templates&amp;#34;),
the label is needed for RTM_NEWCHAIN because tcf_proto_lookup_ops()
may release RTNL to call request_module().&lt;/p&gt;
&lt;p&gt;However, the replay logic is unnecessary for RTM_GETCHAIN.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s apply the replay logic only for RTM_NEWCHAIN.&lt;/p&gt;
&lt;p&gt;[0]:
INFO: task repro:1018 is blocked on a mutex likely owned by task repro:1022.
task:repro           state:R  running task     stack:14096 pid:1022  tgid:1014  ppid:961    task_flags:0x400040 flags:0x00080000
Call Trace:
 &amp;lt;TASK&amp;gt;
 ? clockevents_program_event (kernel/time/clockevents.c:372)
 ? pskb_expand_head (net/core/skbuff.c:615)
 ? skb_release_data (net/core/skbuff.c:1122)
 ? netlink_attachskb (./include/linux/skbuff.h:1323 ./include/linux/skbuff.h:1332 net/netlink/af_netlink.c:1232)
 ? __netlink_lookup (./include/linux/rcupdate.h:882 ./include/linux/rhashtable.h:711 net/netlink/af_netlink.c:499)
 ? tc_chain_notify (ne…&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;net/sched: cls_api: Don&amp;#39;t replay RTM_GETCHAIN in tc_ctl_chain().&lt;/p&gt;
&lt;p&gt;If a netlink socket sends RTM_GETCHAIN requests repeatedly
without recv()ing the responses, tc_ctl_chain() hogs CPU and
triggers Hung Task splat. [0]&lt;/p&gt;
&lt;p&gt;As caught in the stack trace, netlink_attachskb() could confuse
tc_ctl_chain() by returning -EAGAIN when the userspace netlink
socket&amp;#39;s receive buffer is full.&lt;/p&gt;
&lt;p&gt;The replay: label exists since commit 32a4f5ecd738 (&amp;#34;net: sched:
introduce chain object to uapi&amp;#34;) but was not used initially.&lt;/p&gt;
&lt;p&gt;Since commit 9f407f1768d3 (&amp;#34;net: sched: introduce chain templates&amp;#34;),
the label is needed for RTM_NEWCHAIN because tcf_proto_lookup_ops()
may release RTNL to call request_module().&lt;/p&gt;
&lt;p&gt;However, the replay logic is unnecessary for RTM_GETCHAIN.&lt;/p&gt;
&lt;p&gt;Let&amp;#39;s apply the replay logic only for RTM_NEWCHAIN.&lt;/p&gt;
&lt;p&gt;[0]:
INFO: task repro:1018 is blocked on a mutex likely owned by task repro:1022.
task:repro           state:R  running task     stack:14096 pid:1022  tgid:1014  ppid:961    task_flags:0x400040 flags:0x00080000
Call Trace:
 &amp;lt;TASK&amp;gt;
 ? clockevents_program_event (kernel/time/clockevents.c:372)
 ? pskb_expand_head (net/core/skbuff.c:615)
 ? skb_release_data (net/core/skbuff.c:1122)
 ? netlink_attachskb (./include/linux/skbuff.h:1323 ./include/linux/skbuff.h:1332 net/netlink/af_netlink.c:1232)
 ? __netlink_lookup (./include/linux/rcupdate.h:882 ./include/linux/rhashtable.h:711 net/netlink/af_netlink.c:499)
 ? tc_chain_notify (ne…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-wrg6-48wc-j3w4</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-97958</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97958</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_api: Don&amp;#39;t replay RTM_GETCHAIN in tc_ctl_chain(). If a netlink socket sends RTM_GETCHAIN requests repeatedly without recv()ing the responses, tc_ctl_chain() hogs CPU and triggers Hung Task splat. [0] As caught in the stack trace, netlink_attachskb() could confuse tc_ctl_chain() by returning -EAGAIN when the userspace netlink socket&amp;#39;s receive buffer is full. The replay: label exists since commit 32a4f5ecd738 (&amp;#34;net: sched: introduce chain object to uapi&amp;#34;) but was not used initially. Since commit 9f407f1768d3 (&amp;#34;net: sched: introduce chain templates&amp;#34;), the label is needed for RTM_NEWCHAIN because tcf_proto_lookup_ops() may release RTNL to call request_module(). However, the replay logic is unnecessary for RTM_GETCHAIN. Let&amp;#39;s apply the replay logic only for RTM_NEWCHAIN. [0]: INFO: task repro:1018 is blocked on a mutex likely owned by task repro:1022. task:repro           state:R  running task     stack:14096 pid:1022 tgid:1014  ppid:961    task_flags:0x400040 flags:0x00080000 Call Trace:  &amp;lt;TASK&amp;gt;  ? clockevents_program_event (kernel/time/clockevents.c:372)  ? pskb_expand_head (net/core/skbuff.c:615)  ? skb_release_data (net/core/skbuff.c:1122)  ? netlink_attachskb (./include/linux/skbuff.h:1323 ./include/linux/skbuff.h:1332 net/netlink/af_netlink.c:1232)  ? __netlink_lookup (./include/linux/rcupdate.h:882 ./include/linux/rhashtable.h:711 net/netlink/af_netlink.c:499)  ? tc_chain_notify (net/sched/c…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux, 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 and 246 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: net/sched: cls_api: Don&amp;#39;t replay RTM_GETCHAIN in tc_ctl_chain(). If a netlink socket sends RTM_GETCHAIN requests repeatedly without recv()ing the responses, tc_ctl_chain() hogs CPU and triggers Hung Task splat. [0] As caught in the stack trace, netlink_attachskb() could confuse tc_ctl_chain() by returning -EAGAIN when the userspace netlink socket&amp;#39;s receive buffer is full. The replay: label exists since commit 32a4f5ecd738 (&amp;#34;net: sched: introduce chain object to uapi&amp;#34;) but was not used initially. Since commit 9f407f1768d3 (&amp;#34;net: sched: introduce chain templates&amp;#34;), the label is needed for RTM_NEWCHAIN because tcf_proto_lookup_ops() may release RTNL to call request_module(). However, the replay logic is unnecessary for RTM_GETCHAIN. Let&amp;#39;s apply the replay logic only for RTM_NEWCHAIN. [0]: INFO: task repro:1018 is blocked on a mutex likely owned by task repro:1022. task:repro           state:R  running task     stack:14096 pid:1022 tgid:1014  ppid:961    task_flags:0x400040 flags:0x00080000 Call Trace:  &amp;lt;TASK&amp;gt;  ? clockevents_program_event (kernel/time/clockevents.c:372)  ? pskb_expand_head (net/core/skbuff.c:615)  ? skb_release_data (net/core/skbuff.c:1122)  ? netlink_attachskb (./include/linux/skbuff.h:1323 ./include/linux/skbuff.h:1332 net/netlink/af_netlink.c:1232)  ? __netlink_lookup (./include/linux/rcupdate.h:882 ./include/linux/rhashtable.h:711 net/netlink/af_netlink.c:499)  ? tc_chain_notify (net/sched/c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-97958</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3579 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Zustand herbeizuführen oder nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-3579</guid>
    </item>
  </channel>
</rss>
