<?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:02:15 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-06310</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-06310</link>
      <description>bdu:2025-06310</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-06310</guid>
    </item>
    <item>
      <title>BELL-CVE-2023-52929</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2023-52929</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://cve.radiocsirt.org/vuln/bell-cve-2023-52929</guid>
    </item>
    <item>
      <title>EUVD-2026-311761</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-311761</link>
      <description>EUVD-2026-311761</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-311761</guid>
    </item>
    <item>
      <title>fkie_cve-2023-52929</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-52929</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvmem: core: fix cleanup after dev_set_name()&lt;/p&gt;
&lt;p&gt;If dev_set_name() fails, we leak nvmem-&amp;gt;wp_gpio as the cleanup does not
put this. While a minimal fix for this would be to add the gpiod_put()
call, we can do better if we split device_register(), and use the
tested nvmem_release() cleanup code by initialising the device early,
and putting the device.&lt;/p&gt;
&lt;p&gt;This results in a slightly larger fix, but results in clear code.&lt;/p&gt;
&lt;p&gt;Note: this patch depends on &amp;#34;nvmem: core: initialise nvmem-&amp;gt;id early&amp;#34;
and &amp;#34;nvmem: core: remove nvmem_config wp_gpio&amp;#34;.&lt;/p&gt;
&lt;p&gt;[Srini: Fixed subject line and error code handing with wp_gpio while applying.]&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;nvmem: core: fix cleanup after dev_set_name()&lt;/p&gt;
&lt;p&gt;If dev_set_name() fails, we leak nvmem-&amp;gt;wp_gpio as the cleanup does not
put this. While a minimal fix for this would be to add the gpiod_put()
call, we can do better if we split device_register(), and use the
tested nvmem_release() cleanup code by initialising the device early,
and putting the device.&lt;/p&gt;
&lt;p&gt;This results in a slightly larger fix, but results in clear code.&lt;/p&gt;
&lt;p&gt;Note: this patch depends on &amp;#34;nvmem: core: initialise nvmem-&amp;gt;id early&amp;#34;
and &amp;#34;nvmem: core: remove nvmem_config wp_gpio&amp;#34;.&lt;/p&gt;
&lt;p&gt;[Srini: Fixed subject line and error code handing with wp_gpio while applying.]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-52929</guid>
    </item>
    <item>
      <title>GHSA-2g5f-4p47-mx3m</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2g5f-4p47-mx3m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;nvmem: core: fix cleanup after dev_set_name()&lt;/p&gt;
&lt;p&gt;If dev_set_name() fails, we leak nvmem-&amp;gt;wp_gpio as the cleanup does not
put this. While a minimal fix for this would be to add the gpiod_put()
call, we can do better if we split device_register(), and use the
tested nvmem_release() cleanup code by initialising the device early,
and putting the device.&lt;/p&gt;
&lt;p&gt;This results in a slightly larger fix, but results in clear code.&lt;/p&gt;
&lt;p&gt;Note: this patch depends on &amp;#34;nvmem: core: initialise nvmem-&amp;gt;id early&amp;#34;
and &amp;#34;nvmem: core: remove nvmem_config wp_gpio&amp;#34;.&lt;/p&gt;
&lt;p&gt;[Srini: Fixed subject line and error code handing with wp_gpio while applying.]&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;nvmem: core: fix cleanup after dev_set_name()&lt;/p&gt;
&lt;p&gt;If dev_set_name() fails, we leak nvmem-&amp;gt;wp_gpio as the cleanup does not
put this. While a minimal fix for this would be to add the gpiod_put()
call, we can do better if we split device_register(), and use the
tested nvmem_release() cleanup code by initialising the device early,
and putting the device.&lt;/p&gt;
&lt;p&gt;This results in a slightly larger fix, but results in clear code.&lt;/p&gt;
&lt;p&gt;Note: this patch depends on &amp;#34;nvmem: core: initialise nvmem-&amp;gt;id early&amp;#34;
and &amp;#34;nvmem: core: remove nvmem_config wp_gpio&amp;#34;.&lt;/p&gt;
&lt;p&gt;[Srini: Fixed subject line and error code handing with wp_gpio while applying.]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2g5f-4p47-mx3m</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-52929</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52929</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 70 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nvmem: core: fix cleanup after dev_set_name() If dev_set_name() fails, we leak nvmem-&amp;gt;wp_gpio as the cleanup does not put this. While a minimal fix for this would be to add the gpiod_put() call, we can do better if we split device_register(), and use the tested nvmem_release() cleanup code by initialising the device early, and putting the device. This results in a slightly larger fix, but results in clear code. Note: this patch depends on &amp;#34;nvmem: core: initialise nvmem-&amp;gt;id early&amp;#34; and &amp;#34;nvmem: core: remove nvmem_config wp_gpio&amp;#34;. [Srini: Fixed subject line and error code handing with wp_gpio while applying.]&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 70 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: nvmem: core: fix cleanup after dev_set_name() If dev_set_name() fails, we leak nvmem-&amp;gt;wp_gpio as the cleanup does not put this. While a minimal fix for this would be to add the gpiod_put() call, we can do better if we split device_register(), and use the tested nvmem_release() cleanup code by initialising the device early, and putting the device. This results in a slightly larger fix, but results in clear code. Note: this patch depends on &amp;#34;nvmem: core: initialise nvmem-&amp;gt;id early&amp;#34; and &amp;#34;nvmem: core: remove nvmem_config wp_gpio&amp;#34;. [Srini: Fixed subject line and error code handing with wp_gpio while applying.]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2023-52929</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-0649 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0649</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Effekte zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder nicht spezifizierte Effekte zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2025-0649</guid>
    </item>
  </channel>
</rss>
