<?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>Sun, 04 Oct 2026 02:56:10 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-07282</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-07282</link>
      <description>bdu:2025-07282</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-07282</guid>
    </item>
    <item>
      <title>EUVD-2026-309555</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309555</link>
      <description>EUVD-2026-309555</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309555</guid>
    </item>
    <item>
      <title>fkie_cve-2021-47125</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-47125</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sch_htb: fix refcount leak in htb_parent_to_leaf_offload&lt;/p&gt;
&lt;p&gt;The commit ae81feb7338c (&amp;#34;sch_htb: fix null pointer dereference
on a null new_q&amp;#34;) fixes a NULL pointer dereference bug, but it
is not correct.&lt;/p&gt;
&lt;p&gt;Because htb_graft_helper properly handles the case when new_q
is NULL, and after the previous patch by skipping this call
which creates an inconsistency : dev_queue-&amp;gt;qdisc will still
point to the old qdisc, but cl-&amp;gt;parent-&amp;gt;leaf.q will point to
the new one (which will be noop_qdisc, because new_q was NULL).
The code is based on an assumption that these two pointers are
the same, so it can lead to refcount leaks.&lt;/p&gt;
&lt;p&gt;The correct fix is to add a NULL pointer check to protect
qdisc_refcount_inc inside htb_parent_to_leaf_offload.&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;sch_htb: fix refcount leak in htb_parent_to_leaf_offload&lt;/p&gt;
&lt;p&gt;The commit ae81feb7338c (&amp;#34;sch_htb: fix null pointer dereference
on a null new_q&amp;#34;) fixes a NULL pointer dereference bug, but it
is not correct.&lt;/p&gt;
&lt;p&gt;Because htb_graft_helper properly handles the case when new_q
is NULL, and after the previous patch by skipping this call
which creates an inconsistency : dev_queue-&amp;gt;qdisc will still
point to the old qdisc, but cl-&amp;gt;parent-&amp;gt;leaf.q will point to
the new one (which will be noop_qdisc, because new_q was NULL).
The code is based on an assumption that these two pointers are
the same, so it can lead to refcount leaks.&lt;/p&gt;
&lt;p&gt;The correct fix is to add a NULL pointer check to protect
qdisc_refcount_inc inside htb_parent_to_leaf_offload.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-47125</guid>
    </item>
    <item>
      <title>GHSA-6297-42q7-j694</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6297-42q7-j694</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;sch_htb: fix refcount leak in htb_parent_to_leaf_offload&lt;/p&gt;
&lt;p&gt;The commit ae81feb7338c (&amp;#34;sch_htb: fix null pointer dereference
on a null new_q&amp;#34;) fixes a NULL pointer dereference bug, but it
is not correct.&lt;/p&gt;
&lt;p&gt;Because htb_graft_helper properly handles the case when new_q
is NULL, and after the previous patch by skipping this call
which creates an inconsistency : dev_queue-&amp;gt;qdisc will still
point to the old qdisc, but cl-&amp;gt;parent-&amp;gt;leaf.q will point to
the new one (which will be noop_qdisc, because new_q was NULL).
The code is based on an assumption that these two pointers are
the same, so it can lead to refcount leaks.&lt;/p&gt;
&lt;p&gt;The correct fix is to add a NULL pointer check to protect
qdisc_refcount_inc inside htb_parent_to_leaf_offload.&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;sch_htb: fix refcount leak in htb_parent_to_leaf_offload&lt;/p&gt;
&lt;p&gt;The commit ae81feb7338c (&amp;#34;sch_htb: fix null pointer dereference
on a null new_q&amp;#34;) fixes a NULL pointer dereference bug, but it
is not correct.&lt;/p&gt;
&lt;p&gt;Because htb_graft_helper properly handles the case when new_q
is NULL, and after the previous patch by skipping this call
which creates an inconsistency : dev_queue-&amp;gt;qdisc will still
point to the old qdisc, but cl-&amp;gt;parent-&amp;gt;leaf.q will point to
the new one (which will be noop_qdisc, because new_q was NULL).
The code is based on an assumption that these two pointers are
the same, so it can lead to refcount leaks.&lt;/p&gt;
&lt;p&gt;The correct fix is to add a NULL pointer check to protect
qdisc_refcount_inc inside htb_parent_to_leaf_offload.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6297-42q7-j694</guid>
    </item>
    <item>
      <title>gsd-2021-47125</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-47125</link>
      <description>gsd-2021-47125</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-47125</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2021-47125</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47125</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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sch_htb: fix refcount leak in htb_parent_to_leaf_offload The commit ae81feb7338c (&amp;#34;sch_htb: fix null pointer dereference on a null new_q&amp;#34;) fixes a NULL pointer dereference bug, but it is not correct. Because htb_graft_helper properly handles the case when new_q is NULL, and after the previous patch by skipping this call which creates an inconsistency : dev_queue-&amp;gt;qdisc will still point to the old qdisc, but cl-&amp;gt;parent-&amp;gt;leaf.q will point to the new one (which will be noop_qdisc, because new_q was NULL). The code is based on an assumption that these two pointers are the same, so it can lead to refcount leaks. The correct fix is to add a NULL pointer check to protect qdisc_refcount_inc inside htb_parent_to_leaf_offload.&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 54 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: sch_htb: fix refcount leak in htb_parent_to_leaf_offload The commit ae81feb7338c (&amp;#34;sch_htb: fix null pointer dereference on a null new_q&amp;#34;) fixes a NULL pointer dereference bug, but it is not correct. Because htb_graft_helper properly handles the case when new_q is NULL, and after the previous patch by skipping this call which creates an inconsistency : dev_queue-&amp;gt;qdisc will still point to the old qdisc, but cl-&amp;gt;parent-&amp;gt;leaf.q will point to the new one (which will be noop_qdisc, because new_q was NULL). The code is based on an assumption that these two pointers are the same, so it can lead to refcount leaks. The correct fix is to add a NULL pointer check to protect qdisc_refcount_inc inside htb_parent_to_leaf_offload.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-47125</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-0652 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0652</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuführen oder einen nicht 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 einen nicht spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-0652</guid>
    </item>
  </channel>
</rss>
