<?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://127.0.0.1:10001</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, 21 Nov 2026 03:38:23 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-39870</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-39870</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, 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:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2025-39870</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0894 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2025-avi-0894</link>
      <description>certfr-2025-avi-0894</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0894</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-39870</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-39870</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 118 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Fix double free in idxd_setup_wqs() The clean up in idxd_setup_wqs() has had a couple bugs because the error handling is a bit subtle.  It&amp;#39;s simpler to just re-write it in a cleaner way.  The issues here are: 1) If &amp;#34;idxd-&amp;gt;max_wqs&amp;#34; is &amp;lt;= 0 then we call put_device(conf_dev) when    &amp;#34;conf_dev&amp;#34; hasn&amp;#39;t been initialized. 2) If kzalloc_node() fails then again &amp;#34;conf_dev&amp;#34; is invalid.  It&amp;#39;s    either uninitialized or it points to the &amp;#34;conf_dev&amp;#34; from the    previous iteration so it leads to a double free. It&amp;#39;s better to free partial loop iterations within the loop and then the unwinding at the end can handle whole loop iterations.  I also renamed the labels to describe what the goto does and not where the goto was located.&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 118 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Fix double free in idxd_setup_wqs() The clean up in idxd_setup_wqs() has had a couple bugs because the error handling is a bit subtle.  It&amp;#39;s simpler to just re-write it in a cleaner way.  The issues here are: 1) If &amp;#34;idxd-&amp;gt;max_wqs&amp;#34; is &amp;lt;= 0 then we call put_device(conf_dev) when    &amp;#34;conf_dev&amp;#34; hasn&amp;#39;t been initialized. 2) If kzalloc_node() fails then again &amp;#34;conf_dev&amp;#34; is invalid.  It&amp;#39;s    either uninitialized or it points to the &amp;#34;conf_dev&amp;#34; from the    previous iteration so it leads to a double free. It&amp;#39;s better to free partial loop iterations within the loop and then the unwinding at the end can handle whole loop iterations.  I also renamed the labels to describe what the goto does and not where the goto was located.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-39870</guid>
    </item>
  </channel>
</rss>
