<?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>Mon, 12 Oct 2026 09:55:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-41010 — bpf: Fix too early release of tcx_entry</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-41010</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Fix too early release of tcx_entry&lt;/p&gt;
&lt;p&gt;Pedro Pinto and later independently also Hyunwoo Kim and Wongi Lee reported
an issue that the tcx_entry can be released too early leading to a use
after free (UAF) when an active old-style ingress or clsact qdisc with a
shared tc block is later replaced by another ingress or clsact instance.&lt;/p&gt;
&lt;p&gt;Essentially, the sequence to trigger the UAF (one example) can be as follows:&lt;/p&gt;
&lt;p&gt;1. A network namespace is created
  2. An ingress qdisc is created. This allocates a tcx_entry, and
     &amp;amp;tcx_entry-&amp;gt;miniq is stored in the qdisc&amp;#39;s miniqp-&amp;gt;p_miniq. At the
     same time, a tcf block with index 1 is created.
  3. chain0 is attached to the tcf block. chain0 must be connected to
     the block linked to the ingress qdisc to later reach the function
     tcf_chain0_head_change_cb_del() which triggers the UAF.
  4. Create and graft a clsact qdisc. This causes the ingress qdisc
     created in step 1 to be removed, thus freeing the previously linked
     tcx_entry:&lt;/p&gt;
&lt;p&gt;rtnetlink_rcv_msg()
       =&amp;gt; tc_modify_qdisc()
         =&amp;gt; qdisc_create()
           =&amp;gt; clsact_init() [a]
         =&amp;gt; qdisc_graft()
           =&amp;gt; qdisc_destroy()
             =&amp;gt; __qdisc_destroy()
               =&amp;gt; ingress_destroy() [b]
                 =&amp;gt; tcx_entry_free()
                   =&amp;gt; kfree_rcu() // tcx_entry freed&lt;/p&gt;
&lt;p&gt;5. Finally, the network namespace is closed. This registers the
     cleanup_net worker, and d…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;bpf: Fix too early release of tcx_entry&lt;/p&gt;
&lt;p&gt;Pedro Pinto and later independently also Hyunwoo Kim and Wongi Lee reported
an issue that the tcx_entry can be released too early leading to a use
after free (UAF) when an active old-style ingress or clsact qdisc with a
shared tc block is later replaced by another ingress or clsact instance.&lt;/p&gt;
&lt;p&gt;Essentially, the sequence to trigger the UAF (one example) can be as follows:&lt;/p&gt;
&lt;p&gt;1. A network namespace is created
  2. An ingress qdisc is created. This allocates a tcx_entry, and
     &amp;amp;tcx_entry-&amp;gt;miniq is stored in the qdisc&amp;#39;s miniqp-&amp;gt;p_miniq. At the
     same time, a tcf block with index 1 is created.
  3. chain0 is attached to the tcf block. chain0 must be connected to
     the block linked to the ingress qdisc to later reach the function
     tcf_chain0_head_change_cb_del() which triggers the UAF.
  4. Create and graft a clsact qdisc. This causes the ingress qdisc
     created in step 1 to be removed, thus freeing the previously linked
     tcx_entry:&lt;/p&gt;
&lt;p&gt;rtnetlink_rcv_msg()
       =&amp;gt; tc_modify_qdisc()
         =&amp;gt; qdisc_create()
           =&amp;gt; clsact_init() [a]
         =&amp;gt; qdisc_graft()
           =&amp;gt; qdisc_destroy()
             =&amp;gt; __qdisc_destroy()
               =&amp;gt; ingress_destroy() [b]
                 =&amp;gt; tcx_entry_free()
                   =&amp;gt; kfree_rcu() // tcx_entry freed&lt;/p&gt;
&lt;p&gt;5. Finally, the network namespace is closed. This registers the
     cleanup_net worker, and d…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-41010</guid>
    </item>
    <item>
      <title>USN-7089-1 — linux, linux-gcp-6.8, linux-hwe-6.8 vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-7089-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-gcp-6.8, Ubuntu:22.04:LTS: linux-hwe-6.8, Ubuntu:24.04:LTS: linux&lt;/p&gt;
&lt;p&gt;Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel
did not properly check for the device to be enabled before writing. A local
attacker could possibly use this to cause a denial of service. (CVE-2024-25741)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - MIPS architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Cryptographic API;
  - Serial ATA and Parallel ATA drivers;
  - Null block device driver;
  - Bluetooth drivers;
  - Cdrom driver;
  - Clock framework and drivers;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - Cirrus firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - I2C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - ISDN/mISDN subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Fastrpc Driver;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - Near Field Communication (NFC) drivers;
  - NVME drivers;
  - NVMEM (Non Volatile Memory) drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - S/390 drivers;
  - SCSI drivers;
  - Thermal drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB DSL drivers;
  - USB core drivers;
  - DesignWare USB3 driver;
  - USB Gadget dr…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: linux-gcp-6.8, Ubuntu:22.04:LTS: linux-hwe-6.8, Ubuntu:24.04:LTS: linux&lt;/p&gt;
&lt;p&gt;Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel
did not properly check for the device to be enabled before writing. A local
attacker could possibly use this to cause a denial of service. (CVE-2024-25741)&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - ARM32 architecture;
  - MIPS architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Cryptographic API;
  - Serial ATA and Parallel ATA drivers;
  - Null block device driver;
  - Bluetooth drivers;
  - Cdrom driver;
  - Clock framework and drivers;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - Cirrus firmware drivers;
  - GPIO subsystem;
  - GPU drivers;
  - I2C subsystem;
  - IIO subsystem;
  - InfiniBand drivers;
  - ISDN/mISDN subsystem;
  - LED subsystem;
  - Multiple devices driver;
  - Media drivers;
  - Fastrpc Driver;
  - Network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - Near Field Communication (NFC) drivers;
  - NVME drivers;
  - NVMEM (Non Volatile Memory) drivers;
  - PCI subsystem;
  - Pin controllers subsystem;
  - x86 platform drivers;
  - S/390 drivers;
  - SCSI drivers;
  - Thermal drivers;
  - TTY drivers;
  - UFS subsystem;
  - USB DSL drivers;
  - USB core drivers;
  - DesignWare USB3 driver;
  - USB Gadget dr…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-7089-1</guid>
    </item>
  </channel>
</rss>
