<?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-21T07:44:10.901455+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-98818</id>
    <title>BELL-CVE-2026-98818</title>
    <updated>2026-11-21T07:44:10.908712+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:stream: linux-lts</p>
      </div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/bell-cve-2026-98818"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-1537</id>
    <title>certfr-2026-avi-1537 — De multiples vulnérabilités ont été découvertes dans le noyau Linux d'Ubuntu. Certaines d'entre elles permettent à un a…</title>
    <updated>2026-11-21T07:44:10.908769+00:00</updated>
    <content>certfr-2026-avi-1537</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-1537"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-98818</id>
    <title>UBUNTU-CVE-2026-98818</title>
    <updated>2026-11-21T07:44:10.908791+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:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 118 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: mm/slab: do not wake up kswapd in __kfree_rcu_sheaf() Since kfree_rcu() can be called under pi_lock (a raw spinlock in the scheduler), kfree_rcu() itself should never allocate memory with __GFP_KSWAPD_RECLAIM as waking up kswapd ends up acquiring pi_lock, which leads to a deadlock. Reproducing the issue even intentionally was not straightforward. The set_cpus_allowed_force() path that is called under pi_lock is exercised very rarely, and competing tasks that allocate memory will most likely wake kswapd up. Therefore the existence of the deadlock was verified with a modified kernel that has a lockdep map for waking up kswapd:   ======================================================   WARNING: possible circular locking dependency detected   7.2.0-rc1-slab-for-next+ #10 Not tainted   ------------------------------------------------------   git/6660 is trying to acquire lock:   ffff8e524533c550 (&amp;p-&gt;pi_lock){-.-.}-{2:2}, at: _raw_spin_lock_irqsave+0x12/0x20   but task is already holding lock:   ffff8e57bffff1a0 (&amp;pgdat-&gt;kswapd_wait){....}-{3:3}, at: _raw_spin_lock_irqsave+0x12/0x20   which lock already depends on the new lock.   the existing dependency chain (in reverse order) is:   -&gt; #2 (&amp;pgdat-&gt;kswapd_wait){....}-{3:3}:          __lock_acquire+0x5a4/0xc50          lock_acquire.part.0+0xb7/0x240          lock_acquire+0x70/0x170          __raw_spin_lock_irqsave+0x44/0x80          _raw_spin_lock_irqsave+0x12/0x2…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-98818"/>
  </entry>
</feed>
