<?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-21T16:31:39.800721+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:87374</id>
    <title>ALSA-2026:87374 — Important: kernel-rt security update</title>
    <updated>2026-11-21T16:31:39.822470+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> AlmaLinux:8: kernel-rt, AlmaLinux:8: kernel-rt-core, AlmaLinux:8: kernel-rt-debug, AlmaLinux:8: kernel-rt-debug-core, AlmaLinux:8: kernel-rt-debug-devel, AlmaLinux:8: kernel-rt-debug-modules, AlmaLinux:8: kernel-rt-debug-modules-extra, AlmaLinux:8: kernel-rt-devel, AlmaLinux:8: kernel-rt-modules, AlmaLinux:8: kernel-rt-modules-extra</p>
<p>The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.</p>
<p>Security Fix(es):</p>
<p>* kernel: ipv4: raw: reject IP_HDRINCL packets with ihl &lt; 5 (CVE-2026-64114)
  * kernel: fuse: re-lock request before returning from fuse_ref_folio() (CVE-2026-64266)
  * kernel: ipv4: fib: free fib_alias with kfree_rcu() on insert error path (CVE-2026-64572)
  * kernel: ALSA: seq: close a re-opened queue timer in the destructor (CVE-2026-68202)
  * kernel: xfs: bounds-check buffer log item's dirty bitmap (CVE-2026-80536)
  * kernel: inet: frags: strip GSO state from fragments before reassembly (CVE-2026-80590)
  * kernel: vfio/pci: clear vdev-&gt;msi_perm after freeing it on init failure (CVE-2026-89777)</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:87374"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/bell-cve-2026-89777</id>
    <title>BELL-CVE-2026-89777</title>
    <updated>2026-11-21T16:31:39.822552+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-89777"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/certfr-2026-avi-1253</id>
    <title>certfr-2026-avi-1253 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian. Certaines d'entre elles permettent à un…</title>
    <updated>2026-11-21T16:31:39.822574+00:00</updated>
    <content>certfr-2026-avi-1253</content>
    <link href="https://127.0.0.1:10001/vuln/certfr-2026-avi-1253"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/rlsa-2026:87374</id>
    <title>RLSA-2026:87374 — Important: kernel-rt security update</title>
    <updated>2026-11-21T16:31:39.822590+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Rocky Linux:8: kernel-rt, Rocky Linux:8: kernel-rt-core, Rocky Linux:8: kernel-rt-debug, Rocky Linux:8: kernel-rt-debug-core, Rocky Linux:8: kernel-rt-debug-debuginfo, Rocky Linux:8: kernel-rt-debug-devel, Rocky Linux:8: kernel-rt-debuginfo, Rocky Linux:8: kernel-rt-debuginfo-common-x86_64, Rocky Linux:8: kernel-rt-debug-kvm, Rocky Linux:8: kernel-rt-debug-modules and 5 more</p>
<p>The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.</p>
<p>Security Fix(es):</p>
<p>* kernel: ipv4: raw: reject IP_HDRINCL packets with ihl &lt; 5 (CVE-2026-64114)</p>
<p>* kernel: fuse: re-lock request before returning from fuse_ref_folio() (CVE-2026-64266)</p>
<p>* kernel: ipv4: fib: free fib_alias with kfree_rcu() on insert error path (CVE-2026-64572)</p>
<p>* kernel: ALSA: seq: close a re-opened queue timer in the destructor (CVE-2026-68202)</p>
<p>* kernel: xfs: bounds-check buffer log item's dirty bitmap (CVE-2026-80536)</p>
<p>* kernel: inet: frags: strip GSO state from fragments before reassembly (CVE-2026-80590)</p>
<p>* kernel: vfio/pci: clear vdev-&gt;msi_perm after freeing it on init failure (CVE-2026-89777)</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:87374"/>
  </entry>
  <entry>
    <id>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89777</id>
    <title>UBUNTU-CVE-2026-89777</title>
    <updated>2026-11-21T16:31:39.822634+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-aws, Ubuntu:Pro:14.04:LTS: linux-azure, Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:16.04:LTS: linux-hwe-edge and 243 more</p>
<p>In the Linux kernel, the following vulnerability has been resolved: vfio/pci: clear vdev-&gt;msi_perm after freeing it on init failure vfio_msi_cap_len() lazily allocates the per-device MSI permission table: 	vdev-&gt;msi_perm = kmalloc_obj(struct perm_bits, GFP_KERNEL_ACCOUNT); 	if (!vdev-&gt;msi_perm) 		return -ENOMEM; 	ret = init_pci_cap_msi_perm(vdev-&gt;msi_perm, len, flags); 	if (ret) { 		kfree(vdev-&gt;msi_perm); 		return ret;		/* vdev-&gt;msi_perm left dangling */ 	} When init_pci_cap_msi_perm() -&gt; alloc_perm_bits() fails with -ENOMEM, the error path frees vdev-&gt;msi_perm but leaves the freed pointer stored in it. vdev-&gt;msi_perm is not re-zeroed later because struct vfio_pci_core_device is per-device and persists across open/close cycles, and the vfio_config_init() error path returns without calling vfio_config_free(). So the dangling pointer outlives the failed open. That leads to two use-after-frees on the same device: 1. Reuse. The next vfio_config_init() sees the stale pointer at    "if (vdev-&gt;msi_perm) return len;" and reuses the freed object. MSI    config accesses in vfio_pci_config_rw_single() then dereference and    call the freed perm-&gt;readfn / perm-&gt;writefn function pointers. 2. Double free. A later vfio_config_free() runs free_perm_bits() and    kfree() on the already-freed object. Fix it by NULLing vdev-&gt;msi_perm after the kfree(), matching the NULL-after-free discipline already used in free_perm_bits() and vfio_config_free().   BUG: KASAN: slab-use-after-free in vfio_pci_…</p></div>
    </content>
    <link href="https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89777"/>
  </entry>
</feed>
