<?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 12:58:25 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-74321</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-74321</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-2026-74321</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1164 — 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-2026-avi-1164</link>
      <description>certfr-2026-avi-1164</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1164</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-74321</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-74321</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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 220 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() In the beginning of the loop, we try to obtain a locked delayed ref head, if &amp;#39;locked_ref&amp;#39; is currently NULL, by calling btrfs_select_ref_head(), which can return an error pointer. If the error pointer is -EAGAIN we do a continue and go back to the beginning of the loop, which will not try again to call btrfs_select_ref_head() since &amp;#39;locked_ref&amp;#39; is no longer NULL but it&amp;#39;s ERR_PTR(-EAGAIN), and then we do:    spin_lock(&amp;amp;locked_ref-&amp;gt;lock); against a ERR_PTR(-EAGAIN) value, generating an invalid pointer dereference. Fix this by ensuring that &amp;#39;locked_ref&amp;#39; is set to NULL when btrfs_select_ref_head() returns ERR_PTR(-EAGAIN) and incrementing &amp;#39;count&amp;#39; as well, to prevent infinite looping. We do this by doing a goto to the bottom of the loop that already sets &amp;#39;locked_ref&amp;#39; to NULL and does a cond_resched(), with an increment to &amp;#39;count&amp;#39; right before the goto. These measures were in place before the refactoring in commit 0110a4c43451 (&amp;#34;btrfs: refactor __btrfs_run_delayed_refs loop&amp;#34;) but were unintentionally lost afterwards.&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:Pro:18.04:LTS: linux-aws-5.4, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:Pro:18.04:LTS: linux-azure-5.4, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3 and 220 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: btrfs: fix invalid pointer dereference in __btrfs_run_delayed_refs() In the beginning of the loop, we try to obtain a locked delayed ref head, if &amp;#39;locked_ref&amp;#39; is currently NULL, by calling btrfs_select_ref_head(), which can return an error pointer. If the error pointer is -EAGAIN we do a continue and go back to the beginning of the loop, which will not try again to call btrfs_select_ref_head() since &amp;#39;locked_ref&amp;#39; is no longer NULL but it&amp;#39;s ERR_PTR(-EAGAIN), and then we do:    spin_lock(&amp;amp;locked_ref-&amp;gt;lock); against a ERR_PTR(-EAGAIN) value, generating an invalid pointer dereference. Fix this by ensuring that &amp;#39;locked_ref&amp;#39; is set to NULL when btrfs_select_ref_head() returns ERR_PTR(-EAGAIN) and incrementing &amp;#39;count&amp;#39; as well, to prevent infinite looping. We do this by doing a goto to the bottom of the loop that already sets &amp;#39;locked_ref&amp;#39; to NULL and does a cond_resched(), with an increment to &amp;#39;count&amp;#39; right before the goto. These measures were in place before the refactoring in commit 0110a4c43451 (&amp;#34;btrfs: refactor __btrfs_run_delayed_refs loop&amp;#34;) but were unintentionally lost afterwards.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-74321</guid>
    </item>
  </channel>
</rss>
