<?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:24:54 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-23463</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-23463</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-23463</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0547 — 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-2026-avi-0547</link>
      <description>certfr-2026-avi-0547</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0547</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23463</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23463</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 226 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: soc: fsl: qbman: fix race condition in qman_destroy_fq When QMAN_FQ_FLAG_DYNAMIC_FQID is set, there&amp;#39;s a race condition between fq_table[fq-&amp;gt;idx] state and freeing/allocating from the pool and WARN_ON(fq_table[fq-&amp;gt;idx]) in qman_create_fq() gets triggered. Indeed, we can have:          Thread A                             Thread B     qman_destroy_fq()                    qman_create_fq()       qman_release_fqid()         qman_shutdown_fq()         gen_pool_free()            -- At this point, the fqid is available again --                                            qman_alloc_fqid()            -- so, we can get the just-freed fqid in thread B --                                            fq-&amp;gt;fqid = fqid;                                            fq-&amp;gt;idx = fqid * 2;                                            WARN_ON(fq_table[fq-&amp;gt;idx]);                                            fq_table[fq-&amp;gt;idx] = fq;      fq_table[fq-&amp;gt;idx] = NULL; And adding some logs between qman_release_fqid() and fq_table[fq-&amp;gt;idx] = NULL makes the WARN_ON() trigger a lot more. To prevent that, ensure that fq_table[fq-&amp;gt;idx] is set to NULL before gen_pool_free() is called by using smp_wmb().&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-azure, 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, Ubuntu:Pro:16.04:LTS: linux-oracle, Ubuntu:Pro:18.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:18.04:LTS: linux-aws-5.0 and 226 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: soc: fsl: qbman: fix race condition in qman_destroy_fq When QMAN_FQ_FLAG_DYNAMIC_FQID is set, there&amp;#39;s a race condition between fq_table[fq-&amp;gt;idx] state and freeing/allocating from the pool and WARN_ON(fq_table[fq-&amp;gt;idx]) in qman_create_fq() gets triggered. Indeed, we can have:          Thread A                             Thread B     qman_destroy_fq()                    qman_create_fq()       qman_release_fqid()         qman_shutdown_fq()         gen_pool_free()            -- At this point, the fqid is available again --                                            qman_alloc_fqid()            -- so, we can get the just-freed fqid in thread B --                                            fq-&amp;gt;fqid = fqid;                                            fq-&amp;gt;idx = fqid * 2;                                            WARN_ON(fq_table[fq-&amp;gt;idx]);                                            fq_table[fq-&amp;gt;idx] = fq;      fq_table[fq-&amp;gt;idx] = NULL; And adding some logs between qman_release_fqid() and fq_table[fq-&amp;gt;idx] = NULL makes the WARN_ON() trigger a lot more. To prevent that, ensure that fq_table[fq-&amp;gt;idx] is set to NULL before gen_pool_free() is called by using smp_wmb().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-23463</guid>
    </item>
  </channel>
</rss>
