<?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-20T23:56:21.712310+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-53163</id>
    <title>BELL-CVE-2026-53163</title>
    <updated>2026-11-20T23:56:21.733941+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-53163"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0855</id>
    <title>certfr-2026-avi-0855 — De multiples vulnérabilités ont été découvertes dans Microsoft Azure Linux. Elles permettent à un attaquant de provoque…</title>
    <updated>2026-11-20T23:56:21.734002+00:00</updated>
    <content>certfr-2026-avi-0855</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0855"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2026-3205</id>
    <title>OESA-2026-3205 — kernel security update</title>
    <updated>2026-11-20T23:56:21.734025+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>Arm C1-Ultra, C1-Premium, Neoverse V3 &amp;amp; V3AE, Neoverse V2, Neoverse V1, Neoverse-N2, Neoverse-N1, Cortex-X925, Cortex-X4, Cortex-X3, Cortex-X2, Cortex-X1 &amp;amp; X1C, Cortex-A710, Cortex-A78, A78AE &amp;amp; A78C, Cortex-A77, Cortex-A76 &amp;amp; A76A may allow writes to resources owned by a higher exception level.(CVE-2025-10263)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ALSA: ac97: fix a double free in snd_ac97_controller_register()</p>
<p>If ac97_add_adapter() fails, put_device() is the correct way to drop
the device reference. kfree() is not required.
Add kfree() if idr_alloc() fails and in ac97_adapter_release() to do
the cleanup.</p>
<p>Found by code review.(CVE-2025-71192)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak</p>
<p>Fix similar memory leak as in commit 7352e1d5932a (&amp;quot;can: gs_usb:
gs_usb_receive_bulk_callback(): fix URB memory leak&amp;quot;).</p>
<p>In ems_usb_open(), the URBs for USB-in transfers are allocated, added to
the dev-&amp;gt;rx_submitted anchor and submitted. In the complete callback
ems_usb_read_bulk_callback(), the URBs are processed and resubmitted. In
ems_usb_close() the URBs are freed by calling
usb_kill_anchored_urbs(&amp;amp;dev-&amp;gt;rx_submitted).</p>
<p>However, this does not take into account that the USB framework unanchors
the URB before the complete function is called. This means that once a…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-3205"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53163</id>
    <title>UBUNTU-CVE-2026-53163</title>
    <updated>2026-11-20T23:56:21.734081+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 179 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: locking/rtmutex: Skip remove_waiter() when waiter is not enqueued syzbot triggered the following splat in remove_waiter() via FUTEX_CMP_REQUEUE_PI:   KASAN: null-ptr-deref in range [0x0000000000000a88-0x0000000000000a8f]    class_raw_spinlock_constructor    remove_waiter+0x159/0x1200 kernel/locking/rtmutex.c:1561    rt_mutex_start_proxy_lock+0x103/0x120    futex_requeue+0x10e4/0x20d0    __x64_sys_futex+0x34f/0x4d0 task_blocks_on_rt_mutex() does not arm the waiter upon deadlock detection, leaving waiter-&gt;task nil, where 3bfdc63936dd ("rtmutex: Use waiter::task instead of current in remove_waiter()") made this fatal. Furthermore, rt_mutex_start_proxy_lock() should not be calling into remove_waiter() upon a successfully grabbing the rtmutex. 1a1fb985f2e2 ("futex: Handle early deadlock return correctly"), moved the remove_waiter() out of __rt_mutex_start_proxy_lock() (where 'ret' was only ever 0 or &lt; 0) into the wrapper. Tighten this check to account for try_to_take_rt_mutex().</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53163"/>
  </entry>
</feed>
