<?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>Fri, 02 Oct 2026 18:43:33 +0000</lastBuildDate>
    <item>
      <title>certfr-2025-avi-1032 — 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://cve.radiocsirt.org/vuln/certfr-2025-avi-1032</link>
      <description>certfr-2025-avi-1032</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2025-avi-1032</guid>
    </item>
    <item>
      <title>EUVD-2026-311300</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311300</link>
      <description>EUVD-2026-311300</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311300</guid>
    </item>
    <item>
      <title>fkie_cve-2022-50545</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-50545</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;r6040: Fix kmemleak in probe and remove&lt;/p&gt;
&lt;p&gt;There is a memory leaks reported by kmemleak:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888116111000 (size 2048):
    comm &amp;#34;modprobe&amp;#34;, pid 817, jiffies 4294759745 (age 76.502s)
    hex dump (first 32 bytes):
      00 c4 0a 04 81 88 ff ff 08 10 11 16 81 88 ff ff  ................
      08 10 11 16 81 88 ff ff 00 00 00 00 00 00 00 00  ................
    backtrace:
      [&amp;lt;ffffffff815bcd82&amp;gt;] kmalloc_trace+0x22/0x60
      [&amp;lt;ffffffff827e20ee&amp;gt;] phy_device_create+0x4e/0x90
      [&amp;lt;ffffffff827e6072&amp;gt;] get_phy_device+0xd2/0x220
      [&amp;lt;ffffffff827e7844&amp;gt;] mdiobus_scan+0xa4/0x2e0
      [&amp;lt;ffffffff827e8be2&amp;gt;] __mdiobus_register+0x482/0x8b0
      [&amp;lt;ffffffffa01f5d24&amp;gt;] r6040_init_one+0x714/0xd2c [r6040]
      ...&lt;/p&gt;
&lt;p&gt;The problem occurs in probe process as follows:
  r6040_init_one:
    mdiobus_register
      mdiobus_scan    &amp;lt;- alloc and register phy_device,
                         the reference count of phy_device is 3
    r6040_mii_probe
      phy_connect     &amp;lt;- connect to the first phy_device,
                         so the reference count of the first
                         phy_device is 4, others are 3
    register_netdev   &amp;lt;- fault inject succeeded, goto error handling path&lt;/p&gt;
&lt;p&gt;// error handling path
    err_out_mdio_unregister:
      mdiobus_unregister(lp-&amp;gt;mii_bus);
    err_out_mdio:
      mdiobus_free(lp-&amp;gt;mii_bus);    &amp;lt;- the reference count of the first…&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;r6040: Fix kmemleak in probe and remove&lt;/p&gt;
&lt;p&gt;There is a memory leaks reported by kmemleak:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888116111000 (size 2048):
    comm &amp;#34;modprobe&amp;#34;, pid 817, jiffies 4294759745 (age 76.502s)
    hex dump (first 32 bytes):
      00 c4 0a 04 81 88 ff ff 08 10 11 16 81 88 ff ff  ................
      08 10 11 16 81 88 ff ff 00 00 00 00 00 00 00 00  ................
    backtrace:
      [&amp;lt;ffffffff815bcd82&amp;gt;] kmalloc_trace+0x22/0x60
      [&amp;lt;ffffffff827e20ee&amp;gt;] phy_device_create+0x4e/0x90
      [&amp;lt;ffffffff827e6072&amp;gt;] get_phy_device+0xd2/0x220
      [&amp;lt;ffffffff827e7844&amp;gt;] mdiobus_scan+0xa4/0x2e0
      [&amp;lt;ffffffff827e8be2&amp;gt;] __mdiobus_register+0x482/0x8b0
      [&amp;lt;ffffffffa01f5d24&amp;gt;] r6040_init_one+0x714/0xd2c [r6040]
      ...&lt;/p&gt;
&lt;p&gt;The problem occurs in probe process as follows:
  r6040_init_one:
    mdiobus_register
      mdiobus_scan    &amp;lt;- alloc and register phy_device,
                         the reference count of phy_device is 3
    r6040_mii_probe
      phy_connect     &amp;lt;- connect to the first phy_device,
                         so the reference count of the first
                         phy_device is 4, others are 3
    register_netdev   &amp;lt;- fault inject succeeded, goto error handling path&lt;/p&gt;
&lt;p&gt;// error handling path
    err_out_mdio_unregister:
      mdiobus_unregister(lp-&amp;gt;mii_bus);
    err_out_mdio:
      mdiobus_free(lp-&amp;gt;mii_bus);    &amp;lt;- the reference count of the first…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-50545</guid>
    </item>
    <item>
      <title>GHSA-2q87-gcq9-5rfq</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2q87-gcq9-5rfq</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;r6040: Fix kmemleak in probe and remove&lt;/p&gt;
&lt;p&gt;There is a memory leaks reported by kmemleak:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888116111000 (size 2048):
    comm &amp;#34;modprobe&amp;#34;, pid 817, jiffies 4294759745 (age 76.502s)
    hex dump (first 32 bytes):
      00 c4 0a 04 81 88 ff ff 08 10 11 16 81 88 ff ff  ................
      08 10 11 16 81 88 ff ff 00 00 00 00 00 00 00 00  ................
    backtrace:
      [&amp;lt;ffffffff815bcd82&amp;gt;] kmalloc_trace+0x22/0x60
      [&amp;lt;ffffffff827e20ee&amp;gt;] phy_device_create+0x4e/0x90
      [&amp;lt;ffffffff827e6072&amp;gt;] get_phy_device+0xd2/0x220
      [&amp;lt;ffffffff827e7844&amp;gt;] mdiobus_scan+0xa4/0x2e0
      [&amp;lt;ffffffff827e8be2&amp;gt;] __mdiobus_register+0x482/0x8b0
      [&amp;lt;ffffffffa01f5d24&amp;gt;] r6040_init_one+0x714/0xd2c [r6040]
      ...&lt;/p&gt;
&lt;p&gt;The problem occurs in probe process as follows:
  r6040_init_one:
    mdiobus_register
      mdiobus_scan    &amp;lt;- alloc and register phy_device,
                         the reference count of phy_device is 3
    r6040_mii_probe
      phy_connect     &amp;lt;- connect to the first phy_device,
                         so the reference count of the first
                         phy_device is 4, others are 3
    register_netdev   &amp;lt;- fault inject succeeded, goto error handling path&lt;/p&gt;
&lt;p&gt;// error handling path
    err_out_mdio_unregister:
      mdiobus_unregister(lp-&amp;gt;mii_bus);
    err_out_mdio:
      mdiobus_free(lp-&amp;gt;mii_bus);    &amp;lt;- the reference count of the first…&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;r6040: Fix kmemleak in probe and remove&lt;/p&gt;
&lt;p&gt;There is a memory leaks reported by kmemleak:&lt;/p&gt;
&lt;p&gt;unreferenced object 0xffff888116111000 (size 2048):
    comm &amp;#34;modprobe&amp;#34;, pid 817, jiffies 4294759745 (age 76.502s)
    hex dump (first 32 bytes):
      00 c4 0a 04 81 88 ff ff 08 10 11 16 81 88 ff ff  ................
      08 10 11 16 81 88 ff ff 00 00 00 00 00 00 00 00  ................
    backtrace:
      [&amp;lt;ffffffff815bcd82&amp;gt;] kmalloc_trace+0x22/0x60
      [&amp;lt;ffffffff827e20ee&amp;gt;] phy_device_create+0x4e/0x90
      [&amp;lt;ffffffff827e6072&amp;gt;] get_phy_device+0xd2/0x220
      [&amp;lt;ffffffff827e7844&amp;gt;] mdiobus_scan+0xa4/0x2e0
      [&amp;lt;ffffffff827e8be2&amp;gt;] __mdiobus_register+0x482/0x8b0
      [&amp;lt;ffffffffa01f5d24&amp;gt;] r6040_init_one+0x714/0xd2c [r6040]
      ...&lt;/p&gt;
&lt;p&gt;The problem occurs in probe process as follows:
  r6040_init_one:
    mdiobus_register
      mdiobus_scan    &amp;lt;- alloc and register phy_device,
                         the reference count of phy_device is 3
    r6040_mii_probe
      phy_connect     &amp;lt;- connect to the first phy_device,
                         so the reference count of the first
                         phy_device is 4, others are 3
    register_netdev   &amp;lt;- fault inject succeeded, goto error handling path&lt;/p&gt;
&lt;p&gt;// error handling path
    err_out_mdio_unregister:
      mdiobus_unregister(lp-&amp;gt;mii_bus);
    err_out_mdio:
      mdiobus_free(lp-&amp;gt;mii_bus);    &amp;lt;- the reference count of the first…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2q87-gcq9-5rfq</guid>
    </item>
    <item>
      <title>SUSE-SU-2025:4139-1 — Security update for the Linux Kernel</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2025:4139-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://cve.radiocsirt.org/vuln/suse-su-2025:4139-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-50545</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50545</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 157 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: r6040: Fix kmemleak in probe and remove There is a memory leaks reported by kmemleak:   unreferenced object 0xffff888116111000 (size 2048):     comm &amp;#34;modprobe&amp;#34;, pid 817, jiffies 4294759745 (age 76.502s)     hex dump (first 32 bytes):       00 c4 0a 04 81 88 ff ff 08 10 11 16 81 88 ff ff  ................       08 10 11 16 81 88 ff ff 00 00 00 00 00 00 00 00  ................     backtrace:       [&amp;lt;ffffffff815bcd82&amp;gt;] kmalloc_trace+0x22/0x60       [&amp;lt;ffffffff827e20ee&amp;gt;] phy_device_create+0x4e/0x90       [&amp;lt;ffffffff827e6072&amp;gt;] get_phy_device+0xd2/0x220       [&amp;lt;ffffffff827e7844&amp;gt;] mdiobus_scan+0xa4/0x2e0       [&amp;lt;ffffffff827e8be2&amp;gt;] __mdiobus_register+0x482/0x8b0       [&amp;lt;ffffffffa01f5d24&amp;gt;] r6040_init_one+0x714/0xd2c [r6040]       ... The problem occurs in probe process as follows:   r6040_init_one:     mdiobus_register       mdiobus_scan    &amp;lt;- alloc and register phy_device,                          the reference count of phy_device is 3     r6040_mii_probe       phy_connect     &amp;lt;- connect to the first phy_device,                          so the reference count of the first                          phy_device is 4, others are 3     register_netdev   &amp;lt;- fault inject succeeded, goto error handling path     // error handling path     err_out_mdio_unregister:       mdiobus_unregister(lp-&amp;gt;mii_bus);     err_out_mdio:       mdiobus_free(lp-&amp;gt;mii_bus);    &amp;lt;- the reference count of the first…&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:14.04:LTS: linux, Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, 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:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:16.04:LTS: linux and 157 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: r6040: Fix kmemleak in probe and remove There is a memory leaks reported by kmemleak:   unreferenced object 0xffff888116111000 (size 2048):     comm &amp;#34;modprobe&amp;#34;, pid 817, jiffies 4294759745 (age 76.502s)     hex dump (first 32 bytes):       00 c4 0a 04 81 88 ff ff 08 10 11 16 81 88 ff ff  ................       08 10 11 16 81 88 ff ff 00 00 00 00 00 00 00 00  ................     backtrace:       [&amp;lt;ffffffff815bcd82&amp;gt;] kmalloc_trace+0x22/0x60       [&amp;lt;ffffffff827e20ee&amp;gt;] phy_device_create+0x4e/0x90       [&amp;lt;ffffffff827e6072&amp;gt;] get_phy_device+0xd2/0x220       [&amp;lt;ffffffff827e7844&amp;gt;] mdiobus_scan+0xa4/0x2e0       [&amp;lt;ffffffff827e8be2&amp;gt;] __mdiobus_register+0x482/0x8b0       [&amp;lt;ffffffffa01f5d24&amp;gt;] r6040_init_one+0x714/0xd2c [r6040]       ... The problem occurs in probe process as follows:   r6040_init_one:     mdiobus_register       mdiobus_scan    &amp;lt;- alloc and register phy_device,                          the reference count of phy_device is 3     r6040_mii_probe       phy_connect     &amp;lt;- connect to the first phy_device,                          so the reference count of the first                          phy_device is 4, others are 3     register_netdev   &amp;lt;- fault inject succeeded, goto error handling path     // error handling path     err_out_mdio_unregister:       mdiobus_unregister(lp-&amp;gt;mii_bus);     err_out_mdio:       mdiobus_free(lp-&amp;gt;mii_bus);    &amp;lt;- the reference count of the first…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-50545</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2229 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2229</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen und andere nicht näher spezifizierte Angriffe durchzuführen.&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 andere nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-2229</guid>
    </item>
  </channel>
</rss>
