<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://127.0.0.1:10001</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 16:31:38 +0000</lastBuildDate>
    <item>
      <title>ALSA-2026:87374 — Important: kernel-rt security update</title>
      <link>https://127.0.0.1:10001/vuln/alsa-2026:87374</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: raw: reject IP_HDRINCL packets with ihl &amp;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&amp;#39;s dirty bitmap (CVE-2026-80536)
  * kernel: inet: frags: strip GSO state from fragments before reassembly (CVE-2026-80590)
  * kernel: vfio/pci: clear vdev-&amp;gt;msi_perm after freeing it on init failure (CVE-2026-89777)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: raw: reject IP_HDRINCL packets with ihl &amp;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&amp;#39;s dirty bitmap (CVE-2026-80536)
  * kernel: inet: frags: strip GSO state from fragments before reassembly (CVE-2026-80590)
  * kernel: vfio/pci: clear vdev-&amp;gt;msi_perm after freeing it on init failure (CVE-2026-89777)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/alsa-2026:87374</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-89777</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-89777</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-89777</guid>
    </item>
    <item>
      <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>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-1253</link>
      <description>certfr-2026-avi-1253</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-1253</guid>
    </item>
    <item>
      <title>RLSA-2026:87374 — Important: kernel-rt security update</title>
      <link>https://127.0.0.1:10001/vuln/rlsa-2026:87374</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: raw: reject IP_HDRINCL packets with ihl &amp;lt; 5 (CVE-2026-64114)&lt;/p&gt;
&lt;p&gt;* kernel: fuse: re-lock request before returning from fuse_ref_folio() (CVE-2026-64266)&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: fib: free fib_alias with kfree_rcu() on insert error path (CVE-2026-64572)&lt;/p&gt;
&lt;p&gt;* kernel: ALSA: seq: close a re-opened queue timer in the destructor (CVE-2026-68202)&lt;/p&gt;
&lt;p&gt;* kernel: xfs: bounds-check buffer log item&amp;#39;s dirty bitmap (CVE-2026-80536)&lt;/p&gt;
&lt;p&gt;* kernel: inet: frags: strip GSO state from fragments before reassembly (CVE-2026-80590)&lt;/p&gt;
&lt;p&gt;* kernel: vfio/pci: clear vdev-&amp;gt;msi_perm after freeing it on init failure (CVE-2026-89777)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with extremely high determinism requirements.&lt;/p&gt;
&lt;p&gt;Security Fix(es):&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: raw: reject IP_HDRINCL packets with ihl &amp;lt; 5 (CVE-2026-64114)&lt;/p&gt;
&lt;p&gt;* kernel: fuse: re-lock request before returning from fuse_ref_folio() (CVE-2026-64266)&lt;/p&gt;
&lt;p&gt;* kernel: ipv4: fib: free fib_alias with kfree_rcu() on insert error path (CVE-2026-64572)&lt;/p&gt;
&lt;p&gt;* kernel: ALSA: seq: close a re-opened queue timer in the destructor (CVE-2026-68202)&lt;/p&gt;
&lt;p&gt;* kernel: xfs: bounds-check buffer log item&amp;#39;s dirty bitmap (CVE-2026-80536)&lt;/p&gt;
&lt;p&gt;* kernel: inet: frags: strip GSO state from fragments before reassembly (CVE-2026-80590)&lt;/p&gt;
&lt;p&gt;* kernel: vfio/pci: clear vdev-&amp;gt;msi_perm after freeing it on init failure (CVE-2026-89777)&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/rlsa-2026:87374</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-89777</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89777</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vfio/pci: clear vdev-&amp;gt;msi_perm after freeing it on init failure vfio_msi_cap_len() lazily allocates the per-device MSI permission table: 	vdev-&amp;gt;msi_perm = kmalloc_obj(struct perm_bits, GFP_KERNEL_ACCOUNT); 	if (!vdev-&amp;gt;msi_perm) 		return -ENOMEM; 	ret = init_pci_cap_msi_perm(vdev-&amp;gt;msi_perm, len, flags); 	if (ret) { 		kfree(vdev-&amp;gt;msi_perm); 		return ret;		/* vdev-&amp;gt;msi_perm left dangling */ 	} When init_pci_cap_msi_perm() -&amp;gt; alloc_perm_bits() fails with -ENOMEM, the error path frees vdev-&amp;gt;msi_perm but leaves the freed pointer stored in it. vdev-&amp;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    &amp;#34;if (vdev-&amp;gt;msi_perm) return len;&amp;#34; and reuses the freed object. MSI    config accesses in vfio_pci_config_rw_single() then dereference and    call the freed perm-&amp;gt;readfn / perm-&amp;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-&amp;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_…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vfio/pci: clear vdev-&amp;gt;msi_perm after freeing it on init failure vfio_msi_cap_len() lazily allocates the per-device MSI permission table: 	vdev-&amp;gt;msi_perm = kmalloc_obj(struct perm_bits, GFP_KERNEL_ACCOUNT); 	if (!vdev-&amp;gt;msi_perm) 		return -ENOMEM; 	ret = init_pci_cap_msi_perm(vdev-&amp;gt;msi_perm, len, flags); 	if (ret) { 		kfree(vdev-&amp;gt;msi_perm); 		return ret;		/* vdev-&amp;gt;msi_perm left dangling */ 	} When init_pci_cap_msi_perm() -&amp;gt; alloc_perm_bits() fails with -ENOMEM, the error path frees vdev-&amp;gt;msi_perm but leaves the freed pointer stored in it. vdev-&amp;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    &amp;#34;if (vdev-&amp;gt;msi_perm) return len;&amp;#34; and reuses the freed object. MSI    config accesses in vfio_pci_config_rw_single() then dereference and    call the freed perm-&amp;gt;readfn / perm-&amp;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-&amp;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_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-89777</guid>
    </item>
  </channel>
</rss>
