<?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 11:23:07 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-53050</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-53050</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-53050</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://127.0.0.1:10001/vuln/certfr-2026-avi-0862</link>
      <description>certfr-2026-avi-0862</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0862</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-53050</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53050</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 219 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: quota: Fix race of dquot_scan_active() with quota deactivation dquot_scan_active() can race with quota deactivation in quota_release_workfn() like:   CPU0 (quota_release_workfn)         CPU1 (dquot_scan_active)   ==============================      ==============================   spin_lock(&amp;amp;dq_list_lock);   list_replace_init(     &amp;amp;releasing_dquots, &amp;amp;rls_head);     /* dquot X on rls_head,        dq_count == 0,        DQ_ACTIVE_B still set */   spin_unlock(&amp;amp;dq_list_lock);   synchronize_srcu(&amp;amp;dquot_srcu);                                       spin_lock(&amp;amp;dq_list_lock);                                       list_for_each_entry(dquot,                                           &amp;amp;inuse_list, dq_inuse) {                                         /* finds dquot X */                                         dquot_active(X) -&amp;gt; true                                         atomic_inc(&amp;amp;X-&amp;gt;dq_count);                                       }                                       spin_unlock(&amp;amp;dq_list_lock);   spin_lock(&amp;amp;dq_list_lock);   dquot = list_first_entry(&amp;amp;rls_head);   WARN_ON_ONCE(atomic_read(&amp;amp;dquot-&amp;gt;dq_count)); The problem is not only a cosmetic one as under memory pressure the caller of dquot_scan_active() can end up working on freed dquot. Fix the problem by making sure the dquot is removed from releasing list when we acquire a reference to it.&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 219 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: quota: Fix race of dquot_scan_active() with quota deactivation dquot_scan_active() can race with quota deactivation in quota_release_workfn() like:   CPU0 (quota_release_workfn)         CPU1 (dquot_scan_active)   ==============================      ==============================   spin_lock(&amp;amp;dq_list_lock);   list_replace_init(     &amp;amp;releasing_dquots, &amp;amp;rls_head);     /* dquot X on rls_head,        dq_count == 0,        DQ_ACTIVE_B still set */   spin_unlock(&amp;amp;dq_list_lock);   synchronize_srcu(&amp;amp;dquot_srcu);                                       spin_lock(&amp;amp;dq_list_lock);                                       list_for_each_entry(dquot,                                           &amp;amp;inuse_list, dq_inuse) {                                         /* finds dquot X */                                         dquot_active(X) -&amp;gt; true                                         atomic_inc(&amp;amp;X-&amp;gt;dq_count);                                       }                                       spin_unlock(&amp;amp;dq_list_lock);   spin_lock(&amp;amp;dq_list_lock);   dquot = list_first_entry(&amp;amp;rls_head);   WARN_ON_ONCE(atomic_read(&amp;amp;dquot-&amp;gt;dq_count)); The problem is not only a cosmetic one as under memory pressure the caller of dquot_scan_active() can end up working on freed dquot. Fix the problem by making sure the dquot is removed from releasing list when we acquire a reference to it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53050</guid>
    </item>
  </channel>
</rss>
