<?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>Sat, 03 Oct 2026 12:33:05 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-31732</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-31732</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-31732</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0862 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0862</link>
      <description>certfr-2026-avi-0862</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0862</guid>
    </item>
    <item>
      <title>EUVD-2026-332501</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-332501</link>
      <description>EUVD-2026-332501</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-332501</guid>
    </item>
    <item>
      <title>fkie_cve-2026-31732</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-31732</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;gpio: Fix resource leaks on errors in gpiochip_add_data_with_key()&lt;/p&gt;
&lt;p&gt;Since commit aab5c6f20023 (&amp;#34;gpio: set device type for GPIO chips&amp;#34;),
`gdev-&amp;gt;dev.release` is unset.  As a result, the reference count to
`gdev-&amp;gt;dev` isn&amp;#39;t dropped on the error handling paths.&lt;/p&gt;
&lt;p&gt;Drop the reference on errors.&lt;/p&gt;
&lt;p&gt;Also reorder the instructions to make the error handling simpler.
Now gpiochip_add_data_with_key() roughly looks like:&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; Some memory allocation.  Go to ERR ZONE 1 on errors.
   &amp;gt;&amp;gt;&amp;gt; device_initialize().&lt;/p&gt;
&lt;p&gt;gpiodev_release() takes over the responsibility for freeing the
   resources of `gdev-&amp;gt;dev`.  The subsequent error handling paths
   shouldn&amp;#39;t go through ERR ZONE 1 again which leads to double free.&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; Some initialization mainly on `gdev`.
   &amp;gt;&amp;gt;&amp;gt; The rest of initialization.  Go to ERR ZONE 2 on errors.
   &amp;gt;&amp;gt;&amp;gt; Chip registration success and exit.&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; ERR ZONE 2.  gpio_device_put() and exit.
   &amp;gt;&amp;gt;&amp;gt; ERR ZONE 1.&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;gpio: Fix resource leaks on errors in gpiochip_add_data_with_key()&lt;/p&gt;
&lt;p&gt;Since commit aab5c6f20023 (&amp;#34;gpio: set device type for GPIO chips&amp;#34;),
`gdev-&amp;gt;dev.release` is unset.  As a result, the reference count to
`gdev-&amp;gt;dev` isn&amp;#39;t dropped on the error handling paths.&lt;/p&gt;
&lt;p&gt;Drop the reference on errors.&lt;/p&gt;
&lt;p&gt;Also reorder the instructions to make the error handling simpler.
Now gpiochip_add_data_with_key() roughly looks like:&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; Some memory allocation.  Go to ERR ZONE 1 on errors.
   &amp;gt;&amp;gt;&amp;gt; device_initialize().&lt;/p&gt;
&lt;p&gt;gpiodev_release() takes over the responsibility for freeing the
   resources of `gdev-&amp;gt;dev`.  The subsequent error handling paths
   shouldn&amp;#39;t go through ERR ZONE 1 again which leads to double free.&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; Some initialization mainly on `gdev`.
   &amp;gt;&amp;gt;&amp;gt; The rest of initialization.  Go to ERR ZONE 2 on errors.
   &amp;gt;&amp;gt;&amp;gt; Chip registration success and exit.&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; ERR ZONE 2.  gpio_device_put() and exit.
   &amp;gt;&amp;gt;&amp;gt; ERR ZONE 1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-31732</guid>
    </item>
    <item>
      <title>GHSA-fv85-jgqf-p95r</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fv85-jgqf-p95r</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;gpio: Fix resource leaks on errors in gpiochip_add_data_with_key()&lt;/p&gt;
&lt;p&gt;Since commit aab5c6f20023 (&amp;#34;gpio: set device type for GPIO chips&amp;#34;),
`gdev-&amp;gt;dev.release` is unset.  As a result, the reference count to
`gdev-&amp;gt;dev` isn&amp;#39;t dropped on the error handling paths.&lt;/p&gt;
&lt;p&gt;Drop the reference on errors.&lt;/p&gt;
&lt;p&gt;Also reorder the instructions to make the error handling simpler.
Now gpiochip_add_data_with_key() roughly looks like:&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; Some memory allocation.  Go to ERR ZONE 1 on errors.
   &amp;gt;&amp;gt;&amp;gt; device_initialize().&lt;/p&gt;
&lt;p&gt;gpiodev_release() takes over the responsibility for freeing the
   resources of `gdev-&amp;gt;dev`.  The subsequent error handling paths
   shouldn&amp;#39;t go through ERR ZONE 1 again which leads to double free.&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; Some initialization mainly on `gdev`.
   &amp;gt;&amp;gt;&amp;gt; The rest of initialization.  Go to ERR ZONE 2 on errors.
   &amp;gt;&amp;gt;&amp;gt; Chip registration success and exit.&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; ERR ZONE 2.  gpio_device_put() and exit.
   &amp;gt;&amp;gt;&amp;gt; ERR ZONE 1.&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;gpio: Fix resource leaks on errors in gpiochip_add_data_with_key()&lt;/p&gt;
&lt;p&gt;Since commit aab5c6f20023 (&amp;#34;gpio: set device type for GPIO chips&amp;#34;),
`gdev-&amp;gt;dev.release` is unset.  As a result, the reference count to
`gdev-&amp;gt;dev` isn&amp;#39;t dropped on the error handling paths.&lt;/p&gt;
&lt;p&gt;Drop the reference on errors.&lt;/p&gt;
&lt;p&gt;Also reorder the instructions to make the error handling simpler.
Now gpiochip_add_data_with_key() roughly looks like:&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; Some memory allocation.  Go to ERR ZONE 1 on errors.
   &amp;gt;&amp;gt;&amp;gt; device_initialize().&lt;/p&gt;
&lt;p&gt;gpiodev_release() takes over the responsibility for freeing the
   resources of `gdev-&amp;gt;dev`.  The subsequent error handling paths
   shouldn&amp;#39;t go through ERR ZONE 1 again which leads to double free.&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; Some initialization mainly on `gdev`.
   &amp;gt;&amp;gt;&amp;gt; The rest of initialization.  Go to ERR ZONE 2 on errors.
   &amp;gt;&amp;gt;&amp;gt; Chip registration success and exit.&lt;/p&gt;
&lt;p&gt;&amp;gt;&amp;gt;&amp;gt; ERR ZONE 2.  gpio_device_put() and exit.
   &amp;gt;&amp;gt;&amp;gt; ERR ZONE 1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fv85-jgqf-p95r</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-31732</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31732</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 108 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: gpio: Fix resource leaks on errors in gpiochip_add_data_with_key() Since commit aab5c6f20023 (&amp;#34;gpio: set device type for GPIO chips&amp;#34;), `gdev-&amp;gt;dev.release` is unset.  As a result, the reference count to `gdev-&amp;gt;dev` isn&amp;#39;t dropped on the error handling paths. Drop the reference on errors. Also reorder the instructions to make the error handling simpler. Now gpiochip_add_data_with_key() roughly looks like:    &amp;gt;&amp;gt;&amp;gt; Some memory allocation.  Go to ERR ZONE 1 on errors.    &amp;gt;&amp;gt;&amp;gt; device_initialize().    gpiodev_release() takes over the responsibility for freeing the    resources of `gdev-&amp;gt;dev`.  The subsequent error handling paths    shouldn&amp;#39;t go through ERR ZONE 1 again which leads to double free.    &amp;gt;&amp;gt;&amp;gt; Some initialization mainly on `gdev`.    &amp;gt;&amp;gt;&amp;gt; The rest of initialization.  Go to ERR ZONE 2 on errors.    &amp;gt;&amp;gt;&amp;gt; Chip registration success and exit.    &amp;gt;&amp;gt;&amp;gt; ERR ZONE 2.  gpio_device_put() and exit.    &amp;gt;&amp;gt;&amp;gt; ERR ZONE 1.&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 108 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: gpio: Fix resource leaks on errors in gpiochip_add_data_with_key() Since commit aab5c6f20023 (&amp;#34;gpio: set device type for GPIO chips&amp;#34;), `gdev-&amp;gt;dev.release` is unset.  As a result, the reference count to `gdev-&amp;gt;dev` isn&amp;#39;t dropped on the error handling paths. Drop the reference on errors. Also reorder the instructions to make the error handling simpler. Now gpiochip_add_data_with_key() roughly looks like:    &amp;gt;&amp;gt;&amp;gt; Some memory allocation.  Go to ERR ZONE 1 on errors.    &amp;gt;&amp;gt;&amp;gt; device_initialize().    gpiodev_release() takes over the responsibility for freeing the    resources of `gdev-&amp;gt;dev`.  The subsequent error handling paths    shouldn&amp;#39;t go through ERR ZONE 1 again which leads to double free.    &amp;gt;&amp;gt;&amp;gt; Some initialization mainly on `gdev`.    &amp;gt;&amp;gt;&amp;gt; The rest of initialization.  Go to ERR ZONE 2 on errors.    &amp;gt;&amp;gt;&amp;gt; Chip registration success and exit.    &amp;gt;&amp;gt;&amp;gt; ERR ZONE 2.  gpio_device_put() and exit.    &amp;gt;&amp;gt;&amp;gt; ERR ZONE 1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-31732</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1346 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1346</link>
      <description>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Root-Rechte zu erlangen, um Sicherheitsmechanismen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder Auswirkungen unbestimmter Art zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Root-Rechte zu erlangen, um Sicherheitsmechanismen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen oder Auswirkungen unbestimmter Art zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1346</guid>
    </item>
  </channel>
</rss>
