<?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 00:45:29 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2025-38538</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2025-38538</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-38538</guid>
    </item>
    <item>
      <title>certfr-2025-avi-0787 — 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://127.0.0.1:10001/vuln/certfr-2025-avi-0787</link>
      <description>certfr-2025-avi-0787</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2025-avi-0787</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2025-38538</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38538</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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:16.04:LTS: linux-hwe-edge and 214 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dmaengine: nbpfaxi: Fix memory corruption in probe() The nbpf-&amp;gt;chan[] array is allocated earlier in the nbpf_probe() function and it has &amp;#34;num_channels&amp;#34; elements.  These three loops iterate one element farther than they should and corrupt memory. The changes to the second loop are more involved.  In this case, we&amp;#39;re copying data from the irqbuf[] array into the nbpf-&amp;gt;chan[] array.  If the data in irqbuf[i] is the error IRQ then we skip it, so the iterators are not in sync.  I added a check to ensure that we don&amp;#39;t go beyond the end of the irqbuf[] array.  I&amp;#39;m pretty sure this can&amp;#39;t happen, but it seemed harmless to add a check. On the other hand, after the loop has ended there is a check to ensure that the &amp;#34;chan&amp;#34; iterator is where we expect it to be.  In the original code we went one element beyond the end of the array so the iterator wasn&amp;#39;t in the correct place and it would always return -EINVAL.  However, now it will always be in the correct place.  I deleted the check since we know the result.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, 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:16.04:LTS: linux-hwe-edge and 214 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dmaengine: nbpfaxi: Fix memory corruption in probe() The nbpf-&amp;gt;chan[] array is allocated earlier in the nbpf_probe() function and it has &amp;#34;num_channels&amp;#34; elements.  These three loops iterate one element farther than they should and corrupt memory. The changes to the second loop are more involved.  In this case, we&amp;#39;re copying data from the irqbuf[] array into the nbpf-&amp;gt;chan[] array.  If the data in irqbuf[i] is the error IRQ then we skip it, so the iterators are not in sync.  I added a check to ensure that we don&amp;#39;t go beyond the end of the irqbuf[] array.  I&amp;#39;m pretty sure this can&amp;#39;t happen, but it seemed harmless to add a check. On the other hand, after the loop has ended there is a check to ensure that the &amp;#34;chan&amp;#34; iterator is where we expect it to be.  In the original code we went one element beyond the end of the array so the iterator wasn&amp;#39;t in the correct place and it would always return -EINVAL.  However, now it will always be in the correct place.  I deleted the check since we know the result.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2025-38538</guid>
    </item>
  </channel>
</rss>
