<?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:44:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-49927 — x86/ioapic: Handle allocation failures gracefully</title>
      <link>https://db.gcve.eu/vuln/cve-2024-49927</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;x86/ioapic: Handle allocation failures gracefully&lt;/p&gt;
&lt;p&gt;Breno observed panics when using failslab under certain conditions during
runtime:&lt;/p&gt;
&lt;p&gt;can not alloc irq_pin_list (-1,0,20)
   Kernel panic - not syncing: IO-APIC: failed to add irq-pin. Can not proceed&lt;/p&gt;
&lt;p&gt;panic+0x4e9/0x590
   mp_irqdomain_alloc+0x9ab/0xa80
   irq_domain_alloc_irqs_locked+0x25d/0x8d0
   __irq_domain_alloc_irqs+0x80/0x110
   mp_map_pin_to_irq+0x645/0x890
   acpi_register_gsi_ioapic+0xe6/0x150
   hpet_open+0x313/0x480&lt;/p&gt;
&lt;p&gt;That&amp;#39;s a pointless panic which is a leftover of the historic IO/APIC code
which panic&amp;#39;ed during early boot when the interrupt allocation failed.&lt;/p&gt;
&lt;p&gt;The only place which might justify panic is the PIT/HPET timer_check() code
which tries to figure out whether the timer interrupt is delivered through
the IO/APIC. But that code does not require to handle interrupt allocation
failures. If the interrupt cannot be allocated then timer delivery fails
and it either panics due to that or falls back to legacy mode.&lt;/p&gt;
&lt;p&gt;Cure this by removing the panic wrapper around __add_pin_to_irq_node() and
making mp_irqdomain_alloc() aware of the failure condition and handle it as
any other failure in this function gracefully.&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;x86/ioapic: Handle allocation failures gracefully&lt;/p&gt;
&lt;p&gt;Breno observed panics when using failslab under certain conditions during
runtime:&lt;/p&gt;
&lt;p&gt;can not alloc irq_pin_list (-1,0,20)
   Kernel panic - not syncing: IO-APIC: failed to add irq-pin. Can not proceed&lt;/p&gt;
&lt;p&gt;panic+0x4e9/0x590
   mp_irqdomain_alloc+0x9ab/0xa80
   irq_domain_alloc_irqs_locked+0x25d/0x8d0
   __irq_domain_alloc_irqs+0x80/0x110
   mp_map_pin_to_irq+0x645/0x890
   acpi_register_gsi_ioapic+0xe6/0x150
   hpet_open+0x313/0x480&lt;/p&gt;
&lt;p&gt;That&amp;#39;s a pointless panic which is a leftover of the historic IO/APIC code
which panic&amp;#39;ed during early boot when the interrupt allocation failed.&lt;/p&gt;
&lt;p&gt;The only place which might justify panic is the PIT/HPET timer_check() code
which tries to figure out whether the timer interrupt is delivered through
the IO/APIC. But that code does not require to handle interrupt allocation
failures. If the interrupt cannot be allocated then timer delivery fails
and it either panics due to that or falls back to legacy mode.&lt;/p&gt;
&lt;p&gt;Cure this by removing the panic wrapper around __add_pin_to_irq_node() and
making mp_irqdomain_alloc() aware of the failure condition and handle it as
any other failure in this function gracefully.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2024-49927</guid>
    </item>
    <item>
      <title>USN-7166-1 — linux, linux-gcp, linux-gcp-5.15, linux-gke, linux-gkeop, linux-ibm, linux-ibm-5.15, linux-kvm, linux-lowlatency, linux…</title>
      <link>https://db.gcve.eu/vuln/usn-7166-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: linux-gcp-5.15, Ubuntu:20.04:LTS: linux-ibm-5.15, Ubuntu:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:20.04:LTS: linux-oracle-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-gcp, Ubuntu:22.04:LTS: linux-gke, Ubuntu:22.04:LTS: linux-gkeop, Ubuntu:22.04:LTS: linux-ibm, Ubuntu:22.04:LTS: linux-kvm and 4 more&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:
  - ARM32 architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - ACPI drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Buffer Sharing and Synchronization framework;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - I2C subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Mailbox framework;
  - Media drivers;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - STMicroelectronics network drivers;
  - NTB driver;
  - Virtio pmem driver;
  - PCI subsystem;
  - x86 platform drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - SPI subsystem;
  - Thermal drivers;
  - USB Device Class drivers;
  - USB Type-C Port Controller Manager driver;
  - VFIO drivers;
  - Virtio Host (VHOST) subsystem;
  - Framebuffer layer;
  - 9P distributed file system;
  - BTRFS file system;
  - Ceph distributed file system;
  - File systems infrastructure;
  - Ext4 file system;
  - F2FS file system;
  - GFS2 file system;
  - JFS file system;
  - Network file system (NFS) client;
  - Network file system (NFS) server daemon;
  - NILFS2 file system;
  - Network file system (NFS)…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:20.04:LTS: linux-gcp-5.15, Ubuntu:20.04:LTS: linux-ibm-5.15, Ubuntu:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:20.04:LTS: linux-oracle-5.15, Ubuntu:22.04:LTS: linux, Ubuntu:22.04:LTS: linux-gcp, Ubuntu:22.04:LTS: linux-gke, Ubuntu:22.04:LTS: linux-gkeop, Ubuntu:22.04:LTS: linux-ibm, Ubuntu:22.04:LTS: linux-kvm and 4 more&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:
  - ARM32 architecture;
  - RISC-V architecture;
  - S390 architecture;
  - x86 architecture;
  - Block layer subsystem;
  - ACPI drivers;
  - Drivers core;
  - ATA over ethernet (AOE) driver;
  - TPM device driver;
  - Clock framework and drivers;
  - Buffer Sharing and Synchronization framework;
  - EFI core;
  - GPIO subsystem;
  - GPU drivers;
  - HID subsystem;
  - I2C subsystem;
  - InfiniBand drivers;
  - Input Device core drivers;
  - Mailbox framework;
  - Media drivers;
  - Ethernet bonding driver;
  - Network drivers;
  - Mellanox network drivers;
  - Microsoft Azure Network Adapter (MANA) driver;
  - STMicroelectronics network drivers;
  - NTB driver;
  - Virtio pmem driver;
  - PCI subsystem;
  - x86 platform drivers;
  - S/390 drivers;
  - SCSI subsystem;
  - SPI subsystem;
  - Thermal drivers;
  - USB Device Class drivers;
  - USB Type-C Port Controller Manager driver;
  - VFIO drivers;
  - Virtio Host (VHOST) subsystem;
  - Framebuffer layer;
  - 9P distributed file system;
  - BTRFS file system;
  - Ceph distributed file system;
  - File systems infrastructure;
  - Ext4 file system;
  - F2FS file system;
  - GFS2 file system;
  - JFS file system;
  - Network file system (NFS) client;
  - Network file system (NFS) server daemon;
  - NILFS2 file system;
  - Network file system (NFS)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/usn-7166-1</guid>
    </item>
  </channel>
</rss>
