<?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-21T06:52:00.141268+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-43211</id>
    <title>BELL-CVE-2026-43211</title>
    <updated>2026-11-21T06:52:00.155351+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-43211"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0696</id>
    <title>certfr-2026-avi-0696 — 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-21T06:52:00.155426+00:00</updated>
    <content>certfr-2026-avi-0696</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0696"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2026-2673</id>
    <title>OESA-2026-2673 — kernel security update</title>
    <updated>2026-11-21T06:52:00.155447+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:20.03-LTS-SP4: kernel</p>
<p>The Linux Kernel, the operating system core itself.

Security Fix(es):</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>net: hamradio: fix memory leak in mkiss_close</p>
<p>My local syzbot instance hit memory leak in
mkiss_open()[1]. The problem was in missing
free_netdev() in mkiss_close().</p>
<p>In mkiss_open() netdevice is allocated and then
registered, but in mkiss_close() netdevice was
only unregistered, but not freed.</p>
<p>Fail log:</p>
<p>BUG: memory leak
unreferenced object 0xffff8880281ba000 (size 4096):
  comm &amp;quot;syz-executor.1&amp;quot;, pid 11443, jiffies 4295046091 (age 17.660s)
  hex dump (first 32 bytes):
    61 78 30 00 00 00 00 00 00 00 00 00 00 00 00 00  ax0.............
    00 27 fa 2a 80 88 ff ff 00 00 00 00 00 00 00 00  .&amp;apos;.*............
  backtrace:
    [&amp;lt;ffffffff81a27201&amp;gt;] kvmalloc_node+0x61/0xf0
    [&amp;lt;ffffffff8706e7e8&amp;gt;] alloc_netdev_mqs+0x98/0xe80
    [&amp;lt;ffffffff84e64192&amp;gt;] mkiss_open+0xb2/0x6f0 [1]
    [&amp;lt;ffffffff842355db&amp;gt;] tty_ldisc_open+0x9b/0x110
    [&amp;lt;ffffffff84236488&amp;gt;] tty_set_ldisc+0x2e8/0x670
    [&amp;lt;ffffffff8421f7f3&amp;gt;] tty_ioctl+0xda3/0x1440
    [&amp;lt;ffffffff81c9f273&amp;gt;] __x64_sys_ioctl+0x193/0x200
    [&amp;lt;ffffffff8911263a&amp;gt;] do_syscall_64+0x3a/0xb0
    [&amp;lt;ffffffff89200068&amp;gt;] entry_SYSCALL_64_after_hwframe+0x44/0xae</p>
<p>BUG: memory leak
unreferenced object 0xffff8880141a9a00 (size 96):
  comm &amp;quot;syz-executor.1&amp;quot;, pid 11443, jiffies 4295046091 (age 17.660s)
  hex dump (first 32 bytes):
    e8 a2 1…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-2673"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43211</id>
    <title>UBUNTU-CVE-2026-43211</title>
    <updated>2026-11-21T06:52:00.155566+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 197 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: PCI: Fix pci_slot_trylock() error handling Commit a4e772898f8b ("PCI: Add missing bridge lock to pci_bus_lock()") delegates the bridge device's pci_dev_trylock() to pci_bus_trylock() in pci_slot_trylock(), but it forgets to remove the corresponding pci_dev_unlock() when pci_bus_trylock() fails. Before a4e772898f8b, the code did:   if (!pci_dev_trylock(dev)) /* &lt;- lock bridge device */     goto unlock;   if (dev-&gt;subordinate) {     if (!pci_bus_trylock(dev-&gt;subordinate)) {       pci_dev_unlock(dev);   /* &lt;- unlock bridge device */       goto unlock;     }   } After a4e772898f8b the bridge-device lock is no longer taken, but the pci_dev_unlock(dev) on the failure path was left in place, leading to the bug. This yields one of two errors:   1. A warning that the lock is being unlocked when no one holds it.   2. An incorrect unlock of a lock that belongs to another thread. Fix it by removing the now-redundant pci_dev_unlock(dev) on the failure path. [Same patch later posted by Keith at https://patch.msgid.link/20260116184150.3013258-1-kbusch@meta.com]</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-43211"/>
  </entry>
</feed>
