<?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://db.gcve.eu</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>Thu, 19 Nov 2026 17:54:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-89777 — vfio/pci: clear vdev-&gt;msi_perm after freeing it on init failure</title>
      <link>https://db.gcve.eu/vuln/cve-2026-89777</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vfio/pci: clear vdev-&amp;gt;msi_perm after freeing it on init failure&lt;/p&gt;
&lt;p&gt;vfio_msi_cap_len() lazily allocates the per-device MSI permission table:&lt;/p&gt;
&lt;p&gt;vdev-&amp;gt;msi_perm = kmalloc_obj(struct perm_bits, GFP_KERNEL_ACCOUNT);
	if (!vdev-&amp;gt;msi_perm)
		return -ENOMEM;&lt;/p&gt;
&lt;p&gt;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 */
	}&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;That leads to two use-after-frees on the same device:&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;2. Double free. A later vfio_config_free() runs free_perm_bits() and
   kfree() on the already-freed object.&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vfio/pci: clear vdev-&amp;gt;msi_perm after freeing it on init failure&lt;/p&gt;
&lt;p&gt;vfio_msi_cap_len() lazily allocates the per-device MSI permission table:&lt;/p&gt;
&lt;p&gt;vdev-&amp;gt;msi_perm = kmalloc_obj(struct perm_bits, GFP_KERNEL_ACCOUNT);
	if (!vdev-&amp;gt;msi_perm)
		return -ENOMEM;&lt;/p&gt;
&lt;p&gt;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 */
	}&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;That leads to two use-after-frees on the same device:&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;2. Double free. A later vfio_config_free() runs free_perm_bits() and
   kfree() on the already-freed object.&lt;/p&gt;
&lt;p&gt;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().&lt;/p&gt;
&lt;p&gt;BUG: KASAN: slab-use-after-free in…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-89777</guid>
    </item>
    <item>
      <title>USN-8959-1 — linux, linux-aws, linux-gcp, linux-hwe-7.0, linux-ibm, linux-oracle vulnerabilities</title>
      <link>https://db.gcve.eu/vuln/usn-8959-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - USB Gadget drivers;
  - Memory management;
  - Multiple devices driver;
  - ARM64 architecture;
  - EROFS file system;
  - Networking core;
  - eXpress Data Path;
  - ARM32 architecture;
  - M68K architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - Speakup Console Speech Driver;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Auxiliary display drivers;
  - Drivers core;
  - Micron PCIe SSD driver;
  - Null block device driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - AMD CDX bus driver;
  - Hardware random number generator core;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Clocksource drivers;
  - CPU frequency scaling framework;
  - CPU idle management framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - DIBS (Direct Internal Buffer Sharing) drivers;
  - Buffer Sharing and Synchronization framework;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: linux-hwe-7.0, Ubuntu:26.04:LTS: linux, Ubuntu:26.04:LTS: linux-aws, Ubuntu:26.04:LTS: linux-gcp, Ubuntu:26.04:LTS: linux-ibm, Ubuntu:26.04:LTS: linux-oracle&lt;/p&gt;
&lt;p&gt;Several security issues were discovered in the Linux kernel.
An attacker could possibly use these to compromise the system.
This update corrects flaws in the following subsystems:
  - USB Gadget drivers;
  - Memory management;
  - Multiple devices driver;
  - ARM64 architecture;
  - EROFS file system;
  - Networking core;
  - eXpress Data Path;
  - ARM32 architecture;
  - M68K architecture;
  - MIPS architecture;
  - OpenRISC architecture;
  - PA-RISC architecture;
  - PowerPC architecture;
  - RISC-V architecture;
  - S390 architecture;
  - User-Mode Linux (UML);
  - x86 architecture;
  - Block layer subsystem;
  - Cryptographic API;
  - Compute Acceleration Framework;
  - Intel NPU Driver;
  - Speakup Console Speech Driver;
  - ACPI drivers;
  - Serial ATA and Parallel ATA drivers;
  - Auxiliary display drivers;
  - Drivers core;
  - Micron PCIe SSD driver;
  - Null block device driver;
  - Ublk userspace block driver;
  - Compressed RAM block device driver;
  - Bluetooth drivers;
  - Bus devices;
  - AMD CDX bus driver;
  - Hardware random number generator core;
  - Character device driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Clocksource drivers;
  - CPU frequency scaling framework;
  - CPU idle management framework;
  - Hardware crypto device drivers;
  - CXL (Compute Express Link) drivers;
  - DAX dirext access to differentiated memory framework;
  - DIBS (Direct Internal Buffer Sharing) drivers;
  - Buffer Sharing and Synchronization framework;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-8959-1</guid>
    </item>
  </channel>
</rss>
