<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://127.0.0.1:10001/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T11:23:08.028524+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://127.0.0.1:10001" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2026-53050</id>
    <title>BELL-CVE-2026-53050</title>
    <updated>2026-11-21T11:23:08.047422+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2026-53050"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0862</id>
    <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>
    <updated>2026-11-21T11:23:08.047495+00:00</updated>
    <content>certfr-2026-avi-0862</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0862"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53050</id>
    <title>UBUNTU-CVE-2026-53050</title>
    <updated>2026-11-21T11:23:08.047517+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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;dq_list_lock);   list_replace_init(     &amp;releasing_dquots, &amp;rls_head);     /* dquot X on rls_head,        dq_count == 0,        DQ_ACTIVE_B still set */   spin_unlock(&amp;dq_list_lock);   synchronize_srcu(&amp;dquot_srcu);                                       spin_lock(&amp;dq_list_lock);                                       list_for_each_entry(dquot,                                           &amp;inuse_list, dq_inuse) {                                         /* finds dquot X */                                         dquot_active(X) -&gt; true                                         atomic_inc(&amp;X-&gt;dq_count);                                       }                                       spin_unlock(&amp;dq_list_lock);   spin_lock(&amp;dq_list_lock);   dquot = list_first_entry(&amp;rls_head);   WARN_ON_ONCE(atomic_read(&amp;dquot-&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.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53050"/>
  </entry>
</feed>
