<?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-21T01:06:54.701878+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/alsa-2026:63128</id>
    <title>ALSA-2026:63128 — Important: kernel security update</title>
    <updated>2026-11-21T01:06:54.724484+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:10: kernel-abi-stablelists, AlmaLinux:10: kernel-doc</p>
<p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p>
<p>Security Fix(es):</p>
<p>* kernel: Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error (CVE-2026-53073)
  * kernel: exfat: fix potential use-after-free in exfat_find_dir_entry() (CVE-2026-63808)
  * kernel: KEYS: fix overflow in keyctl_pkey_params_get_2() (CVE-2026-63824)
  * kernel: smb: client: fix query directory replay double-free (CVE-2026-64387)
  * kernel: iomap: fix out-of-bounds bitmap_set() with zero-length range (CVE-2026-68145)
  * kernel: net: ipv6: use-after-free in fib6_rule_suppress due to stale res-&gt;rt6 pointer (CVE-2026-74581)</p>
<p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/alsa-2026:63128"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2026-53073</id>
    <title>BELL-CVE-2026-53073</title>
    <updated>2026-11-21T01:06:54.724542+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-53073"/>
  </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-21T01:06:54.724561+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/oesa-2026-3529</id>
    <title>OESA-2026-3529 — kernel security update</title>
    <updated>2026-11-21T01:06:54.724575+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS-SP1: 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>thermal: core: Fix thermal zone governor cleanup issues</p>
<p>If thermal_zone_device_register_with_trips() fails after adding
a thermal governor to the thermal zone being registered, the
governor is not removed from it as appropriate which may lead to
a memory leak.</p>
<p>In turn, thermal_zone_device_unregister() calls thermal_set_governor()
without acquiring the thermal zone lock beforehand which may race with
a governor update via sysfs and may lead to a use-after-free in that
case.</p>
<p>Address these issues by adding two thermal_set_governor() calls, one to
thermal_release() to remove the governor from the given thermal zone,
and one to the thermal zone registration error path to cover failures
preceding the thermal zone device registration.(CVE-2026-46021)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>crypto: authencesn - reject short ahash digests during instance creation</p>
<p>authencesn requires either a zero authsize or an authsize of at least
4 bytes because the ESN encrypt/decrypt paths always move 4 bytes of
high-order sequence number data at the end of the authenticated data.</p>
<p>While crypto_authenc_esn_setauthsize() already rejects explicit
non-zero authsizes in the range 1..3, crypto_authenc_esn_create()
still copied auth-&amp;gt;digestsize into inst-&amp;gt;alg.maxauthsize without
validating it.  The AEAD core then initializ…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-3529"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rlsa-2026:63128</id>
    <title>RLSA-2026:63128 — Important: kernel security update</title>
    <updated>2026-11-21T01:06:54.724622+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Rocky Linux:10: kernel-tools-debuginfo, Rocky Linux:10: kernel-tools-libs-devel, Rocky Linux:10: kernel-rt-debug-modules, Rocky Linux:10: kernel-debug-core, Rocky Linux:10: kernel-debug-debuginfo, Rocky Linux:10: kernel-debug-modules-core, Rocky Linux:10: kernel-debug-modules, Rocky Linux:10: kernel-debug, Rocky Linux:10: kernel-modules-core, Rocky Linux:10: rtla and 80 more</p>
<p>The kernel packages contain the Linux kernel, the core of any Linux operating system.</p>
<p>Security Fix(es):</p>
<p>* kernel: Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error (CVE-2026-53073)</p>
<p>* kernel: exfat: fix potential use-after-free in exfat_find_dir_entry() (CVE-2026-63808)</p>
<p>* kernel: KEYS: fix overflow in keyctl_pkey_params_get_2() (CVE-2026-63824)</p>
<p>* kernel: smb: client: fix query directory replay double-free (CVE-2026-64387)</p>
<p>* kernel: iomap: fix out-of-bounds bitmap_set() with zero-length range (CVE-2026-68145)</p>
<p>* kernel: net: ipv6: use-after-free in fib6_rule_suppress due to stale res-&gt;rt6 pointer (CVE-2026-74581)</p>
<p>For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rlsa-2026:63128"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53073</id>
    <title>UBUNTU-CVE-2026-53073</title>
    <updated>2026-11-21T01:06:54.724738+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 197 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error When hci_register_dev() fails in hci_uart_register_dev() HCI_UART_PROTO_INIT is not cleared before calling hu-&gt;proto-&gt;close(hu) and setting hu-&gt;hdev to NULL. This means incoming UART data will reach the protocol-specific recv handler in hci_uart_tty_receive() after resources are freed. Clear HCI_UART_PROTO_INIT with a write lock before calling hu-&gt;proto-&gt;close() and setting hu-&gt;hdev to NULL. The write lock ensures all active readers have completed and no new reader can enter the protocol recv path before resources are freed. This allows the protocol-specific recv functions to remove the "HCI_UART_REGISTERED" guard without risking a null pointer dereference if hci_register_dev() fails.</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-53073"/>
  </entry>
</feed>
