<?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-21T02:11:03.115652+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:83207</id>
    <title>ALSA-2026:83207 — Important: kernel security, bug fix, and enhancement update</title>
    <updated>2026-11-21T02:11:03.128575+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: netfilter: nfnetlink_queue: do shared-unconfirmed check before segmentation (CVE-2026-45859)
  * kernel: net/sched: act_ct: Only release RCU read lock after ct_ft (CVE-2026-46319)
  * kernel: net/sched: taprio: fix use-after-free in advance_sched() on schedule switch (CVE-2026-53011)
  * kernel: USB: serial: mxuport: fix memory corruption with small endpoint (CVE-2026-63899)
  * kernel: bridge: mcast: Fix a possible use-after-free when removing a bridge port (CVE-2026-64032)
  * kernel: wifi: mac80211: bounds-check link_id in ieee80211_ml_epcs (CVE-2026-64030)
  * kernel: Bluetooth: hci_sync: Set HCI_CMD_DRAIN_WORKQUEUE during device close (CVE-2026-63974)
  * kernel: idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() (CVE-2026-64162)
  * kernel: Linux kernel: Denial of Service due to use-after-free in act_tunnel_key (CVE-2026-68377)
  * kernel: net/iucv: fix use-after-free of a severed iucv_path (CVE-2026-68140)
  * kernel: ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get (CVE-2026-72262)
  * kernel: dmaengine: idxd: fix fdev setup failure cleanup in idxd_cdev_open() (CVE-2026-74574)
  * kernel: ALSA: usx2y: bound the hwdep mmap fault offset (CVE-2026-74641)
  * kernel: net/smc: carry oversized SMC-Rv2 LLC messages in the queue entry (CVE-2026-80985)
  * kernel: svcrdma: Validate Read chunk positions before reconstruction (CVE-20…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/alsa-2026:83207"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2026-64032</id>
    <title>BELL-CVE-2026-64032</title>
    <updated>2026-11-21T02:11:03.128635+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-64032"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-0926</id>
    <title>certfr-2026-avi-0926 — 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-21T02:11:03.128655+00:00</updated>
    <content>certfr-2026-avi-0926</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-0926"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/oesa-2026-3704</id>
    <title>OESA-2026-3704 — kernel security update</title>
    <updated>2026-11-21T02:11:03.128667+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:24.03-LTS-SP3: 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: hns3: add VLAN id validation before using</p>
<p>Currently, the VLAN id may be used without validation when
receive a VLAN configuration mailbox from VF. The length of
vlan_del_fail_bmap is BITS_TO_LONGS(VLAN_N_VID). It may cause
out-of-bounds memory access once the VLAN id is bigger than
or equal to VLAN_N_VID.</p>
<p>Therefore, VLAN id needs to be checked to ensure it is within
the range of VLAN_N_VID.(CVE-2025-71112)</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>ext4: fix string copying in parse_apply_sb_mount_options()</p>
<p>strscpy_pad() can&amp;apos;t be used to copy a non-NUL-term string into a NUL-term
string of possibly bigger size.  Commit 0efc5990bca5 (&amp;quot;string.h: Introduce
memtostr() and memtostr_pad()&amp;quot;) provides additional information in that
regard.  So if this happens, the following warning is observed:</p>
<p>strnlen: detected buffer overflow: 65 byte read of buffer size 64
WARNING: CPU: 0 PID: 28655 at lib/string_helpers.c:1032 __fortify_report+0x96/0xc0 lib/string_helpers.c:1032
Modules linked in:
CPU: 0 UID: 0 PID: 28655 Comm: syz-executor.3 Not tainted 6.12.54-syzkaller-00144-g5f0270f1ba00 #0
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
RIP: 0010:__fortify_report+0x96/0xc0 lib/string_helpers.c:1032
Call Trace:
 &amp;lt;TASK&amp;gt;
 __fortify_panic+0x1f/0x30 lib/s…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/oesa-2026-3704"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rlsa-2026:83207</id>
    <title>RLSA-2026:83207 — Important: kernel security, bug fix, and enhancement update</title>
    <updated>2026-11-21T02:11:03.129483+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Rocky Linux:10: kernel-devel-matched, Rocky Linux:10: perf-debuginfo, Rocky Linux:10: kernel-devel, Rocky Linux:10: kernel-zfcpdump-modules, Rocky Linux:10: kernel-debug-core, Rocky Linux:10: kernel-tools, Rocky Linux:10: kernel-debug, Rocky Linux:10: libperf, Rocky Linux:10: rv, Rocky Linux:10: kernel-debug-debuginfo 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: netfilter: nfnetlink_queue: do shared-unconfirmed check before segmentation (CVE-2026-45859)</p>
<p>* kernel: net/sched: act_ct: Only release RCU read lock after ct_ft (CVE-2026-46319)</p>
<p>* kernel: net/sched: taprio: fix use-after-free in advance_sched() on schedule switch (CVE-2026-53011)</p>
<p>* kernel: USB: serial: mxuport: fix memory corruption with small endpoint (CVE-2026-63899)</p>
<p>* kernel: bridge: mcast: Fix a possible use-after-free when removing a bridge port (CVE-2026-64032)</p>
<p>* kernel: wifi: mac80211: bounds-check link_id in ieee80211_ml_epcs (CVE-2026-64030)</p>
<p>* kernel: Bluetooth: hci_sync: Set HCI_CMD_DRAIN_WORKQUEUE during device close (CVE-2026-63974)</p>
<p>* kernel: idpf: fix read_dev_clk_lock spinlock init in idpf_ptp_init() (CVE-2026-64162)</p>
<p>* kernel: Linux kernel: Denial of Service due to use-after-free in act_tunnel_key (CVE-2026-68377)</p>
<p>* kernel: net/iucv: fix use-after-free of a severed iucv_path (CVE-2026-68140)</p>
<p>* kernel: ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get (CVE-2026-72262)</p>
<p>* kernel: dmaengine: idxd: fix fdev setup failure cleanup in idxd_cdev_open() (CVE-2026-74574)</p>
<p>* kernel: ALSA: usx2y: bound the hwdep mmap fault offset (CVE-2026-74641)</p>
<p>* kernel: net/smc: carry oversized SMC-Rv2 LLC messages in the queue entry (CVE-2026-80985)</p>
<p>* kernel: svcrdma: Validate Read chunk positions before reconstruction (CVE-2026-89526)</p>
<p>* kernel:…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/rlsa-2026:83207"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64032</id>
    <title>UBUNTU-CVE-2026-64032</title>
    <updated>2026-11-21T02:11:03.129614+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 189 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: bridge: mcast: Fix a possible use-after-free when removing a bridge port When per-VLAN multicast snooping is enabled, the bridge iterates over all the bridge ports, disables the per-port multicast context on each port and enables the per-{port, VLAN} multicast contexts instead. The reverse happens when per-VLAN multicast snooping is disabled. When global multicast snooping is enabled, the bridge iterates over all the bridge ports and enables the per-port multicast context on each port. The reverse happens when multicast snooping is disabled. The above scheme can result in a situation where both types of contexts (per-port and per-{port, VLAN}) are enabled on a single bridge port:  # ip link add name br1 up type bridge mcast_snooping 1 mcast_querier 1 vlan_filtering 1  # ip link add name dummy1 up master br1 type dummy  # ip link set dev br1 type bridge mcast_vlan_snooping 1  # ip link set dev br1 type bridge mcast_snooping 0  # ip link set dev br1 type bridge mcast_snooping 1 This is not intended and it is a problem since the commit cited below. Prior to this commit, when removing a bridge port, br_multicast_disable_port() would disable the per-port multicast context and the per-{port, VLAN} multicast contexts would get disabled when flushing VLANs. After this commit, br_multicast_disable_port() only disables the per-port multicast context if per-VLAN multicast snooping is disabled. If both types of contexts…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-64032"/>
  </entry>
</feed>
