<?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>Wed, 30 Sep 2026 13:43:33 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-01209</title>
      <link>https://db.gcve.eu/vuln/bdu:2026-01209</link>
      <description>bdu:2026-01209</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/bdu:2026-01209</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0108 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de SUSE. Certaines d'entre elles permettent à un at…</title>
      <link>https://db.gcve.eu/vuln/certfr-2026-avi-0108</link>
      <description>certfr-2026-avi-0108</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2026-avi-0108</guid>
    </item>
    <item>
      <title>fkie_cve-2023-54137</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2023-54137</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vfio/type1: fix cap_migration information leak&lt;/p&gt;
&lt;p&gt;Fix an information leak where an uninitialized hole in struct
vfio_iommu_type1_info_cap_migration on the stack is exposed to userspace.&lt;/p&gt;
&lt;p&gt;The definition of struct vfio_iommu_type1_info_cap_migration contains a hole as
shown in this pahole(1) output:&lt;/p&gt;
&lt;p&gt;struct vfio_iommu_type1_info_cap_migration {
          struct vfio_info_cap_header header;              /*     0     8 */
          __u32                      flags;                /*     8     4 */&lt;/p&gt;
&lt;p&gt;/* XXX 4 bytes hole, try to pack */&lt;/p&gt;
&lt;p&gt;__u64                      pgsize_bitmap;        /*    16     8 */
          __u64                      max_dirty_bitmap_size; /*    24     8 */&lt;/p&gt;
&lt;p&gt;/* size: 32, cachelines: 1, members: 4 */
          /* sum members: 28, holes: 1, sum holes: 4 */
          /* last cacheline: 32 bytes */
  };&lt;/p&gt;
&lt;p&gt;The cap_mig variable is filled in without initializing the hole:&lt;/p&gt;
&lt;p&gt;static int vfio_iommu_migration_build_caps(struct vfio_iommu *iommu,
                         struct vfio_info_cap *caps)
  {
      struct vfio_iommu_type1_info_cap_migration cap_mig;&lt;/p&gt;
&lt;p&gt;cap_mig.header.id = VFIO_IOMMU_TYPE1_INFO_CAP_MIGRATION;
      cap_mig.header.version = 1;&lt;/p&gt;
&lt;p&gt;cap_mig.flags = 0;
      /* support minimum pgsize */
      cap_mig.pgsize_bitmap = (size_t)1 &amp;lt;&amp;lt; __ffs(iommu-&amp;gt;pgsize_bitmap);
      cap_mig.max_dirty_bitmap_size = DIRTY_BITMAP_SIZE_MAX;&lt;/p&gt;
&lt;p&gt;return vfio_info_add_…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vfio/type1: fix cap_migration information leak&lt;/p&gt;
&lt;p&gt;Fix an information leak where an uninitialized hole in struct
vfio_iommu_type1_info_cap_migration on the stack is exposed to userspace.&lt;/p&gt;
&lt;p&gt;The definition of struct vfio_iommu_type1_info_cap_migration contains a hole as
shown in this pahole(1) output:&lt;/p&gt;
&lt;p&gt;struct vfio_iommu_type1_info_cap_migration {
          struct vfio_info_cap_header header;              /*     0     8 */
          __u32                      flags;                /*     8     4 */&lt;/p&gt;
&lt;p&gt;/* XXX 4 bytes hole, try to pack */&lt;/p&gt;
&lt;p&gt;__u64                      pgsize_bitmap;        /*    16     8 */
          __u64                      max_dirty_bitmap_size; /*    24     8 */&lt;/p&gt;
&lt;p&gt;/* size: 32, cachelines: 1, members: 4 */
          /* sum members: 28, holes: 1, sum holes: 4 */
          /* last cacheline: 32 bytes */
  };&lt;/p&gt;
&lt;p&gt;The cap_mig variable is filled in without initializing the hole:&lt;/p&gt;
&lt;p&gt;static int vfio_iommu_migration_build_caps(struct vfio_iommu *iommu,
                         struct vfio_info_cap *caps)
  {
      struct vfio_iommu_type1_info_cap_migration cap_mig;&lt;/p&gt;
&lt;p&gt;cap_mig.header.id = VFIO_IOMMU_TYPE1_INFO_CAP_MIGRATION;
      cap_mig.header.version = 1;&lt;/p&gt;
&lt;p&gt;cap_mig.flags = 0;
      /* support minimum pgsize */
      cap_mig.pgsize_bitmap = (size_t)1 &amp;lt;&amp;lt; __ffs(iommu-&amp;gt;pgsize_bitmap);
      cap_mig.max_dirty_bitmap_size = DIRTY_BITMAP_SIZE_MAX;&lt;/p&gt;
&lt;p&gt;return vfio_info_add_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2023-54137</guid>
    </item>
    <item>
      <title>GHSA-78pw-r9wg-6p38</title>
      <link>https://db.gcve.eu/vuln/ghsa-78pw-r9wg-6p38</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vfio/type1: fix cap_migration information leak&lt;/p&gt;
&lt;p&gt;Fix an information leak where an uninitialized hole in struct
vfio_iommu_type1_info_cap_migration on the stack is exposed to userspace.&lt;/p&gt;
&lt;p&gt;The definition of struct vfio_iommu_type1_info_cap_migration contains a hole as
shown in this pahole(1) output:&lt;/p&gt;
&lt;p&gt;struct vfio_iommu_type1_info_cap_migration {
          struct vfio_info_cap_header header;              /*     0     8 */
          __u32                      flags;                /*     8     4 */&lt;/p&gt;
&lt;p&gt;/* XXX 4 bytes hole, try to pack */&lt;/p&gt;
&lt;p&gt;__u64                      pgsize_bitmap;        /*    16     8 */
          __u64                      max_dirty_bitmap_size; /*    24     8 */&lt;/p&gt;
&lt;p&gt;/* size: 32, cachelines: 1, members: 4 */
          /* sum members: 28, holes: 1, sum holes: 4 */
          /* last cacheline: 32 bytes */
  };&lt;/p&gt;
&lt;p&gt;The cap_mig variable is filled in without initializing the hole:&lt;/p&gt;
&lt;p&gt;static int vfio_iommu_migration_build_caps(struct vfio_iommu *iommu,
                         struct vfio_info_cap *caps)
  {
      struct vfio_iommu_type1_info_cap_migration cap_mig;&lt;/p&gt;
&lt;p&gt;cap_mig.header.id = VFIO_IOMMU_TYPE1_INFO_CAP_MIGRATION;
      cap_mig.header.version = 1;&lt;/p&gt;
&lt;p&gt;cap_mig.flags = 0;
      /* support minimum pgsize */
      cap_mig.pgsize_bitmap = (size_t)1 &amp;lt;&amp;lt; __ffs(iommu-&amp;gt;pgsize_bitmap);
      cap_mig.max_dirty_bitmap_size = DIRTY_BITMAP_SIZE_MAX;&lt;/p&gt;
&lt;p&gt;return vfio_info_add_…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;vfio/type1: fix cap_migration information leak&lt;/p&gt;
&lt;p&gt;Fix an information leak where an uninitialized hole in struct
vfio_iommu_type1_info_cap_migration on the stack is exposed to userspace.&lt;/p&gt;
&lt;p&gt;The definition of struct vfio_iommu_type1_info_cap_migration contains a hole as
shown in this pahole(1) output:&lt;/p&gt;
&lt;p&gt;struct vfio_iommu_type1_info_cap_migration {
          struct vfio_info_cap_header header;              /*     0     8 */
          __u32                      flags;                /*     8     4 */&lt;/p&gt;
&lt;p&gt;/* XXX 4 bytes hole, try to pack */&lt;/p&gt;
&lt;p&gt;__u64                      pgsize_bitmap;        /*    16     8 */
          __u64                      max_dirty_bitmap_size; /*    24     8 */&lt;/p&gt;
&lt;p&gt;/* size: 32, cachelines: 1, members: 4 */
          /* sum members: 28, holes: 1, sum holes: 4 */
          /* last cacheline: 32 bytes */
  };&lt;/p&gt;
&lt;p&gt;The cap_mig variable is filled in without initializing the hole:&lt;/p&gt;
&lt;p&gt;static int vfio_iommu_migration_build_caps(struct vfio_iommu *iommu,
                         struct vfio_info_cap *caps)
  {
      struct vfio_iommu_type1_info_cap_migration cap_mig;&lt;/p&gt;
&lt;p&gt;cap_mig.header.id = VFIO_IOMMU_TYPE1_INFO_CAP_MIGRATION;
      cap_mig.header.version = 1;&lt;/p&gt;
&lt;p&gt;cap_mig.flags = 0;
      /* support minimum pgsize */
      cap_mig.pgsize_bitmap = (size_t)1 &amp;lt;&amp;lt; __ffs(iommu-&amp;gt;pgsize_bitmap);
      cap_mig.max_dirty_bitmap_size = DIRTY_BITMAP_SIZE_MAX;&lt;/p&gt;
&lt;p&gt;return vfio_info_add_…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-78pw-r9wg-6p38</guid>
    </item>
    <item>
      <title>RHSA-2024:2394 — Red Hat Security Advisory: kernel security, bug fix, and enhancement update</title>
      <link>https://db.gcve.eu/vuln/rhsa-2024:2394</link>
      <description>&lt;p&gt;kernel: Bluetooth BR/EDR PIN Pairing procedure is vulnerable to an impersonation attack kernel: ovl: fix warning in ovl_create_real() kernel: memcg does not limit the number of POSIX file locks allowing memory exhaustion kernel: vmwgfx: NULL pointer dereference in vmw_cmd_dx_define_query kernel: integer overflow in l2cap_config_req() in net/bluetooth/l2cap_core.c kernel: i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() kernel: Bluetooth: L2CAP: Fix u8 overflow kernel: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() kernel: tracing: Fix sleeping function called from invalid context on RT kernel kernel: net: mdio: unexport __init-annotated mdio_bus_init() kernel: arm64: ftrace: consistently handle PLTs. kernel: mm/uffd: fix pte marker when fork() without fork event kernel: Bluetooth: Fix a buffer overflow in mgmt_mesh_add() kernel: tty: n_gsm: add sanity check for gsm-&amp;gt;receive in gsm_receive_buf() kernel: ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead kernel: tee: add overflow check in register_shm_helper() kernel: tty: n_gsm: fix deadlock and link starvation in outgoing data path kernel: PM: hibernate: defer device probing when resuming from hibernation kernel: ext4: don&amp;#39;t allow journal inode to have encrypt flag kernel: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline kernel: erofs: fix order &amp;gt;= MAX_ORDER warning due to crafted negative i_size kernel: perf/x86/intel/uncore: F…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel: Bluetooth BR/EDR PIN Pairing procedure is vulnerable to an impersonation attack kernel: ovl: fix warning in ovl_create_real() kernel: memcg does not limit the number of POSIX file locks allowing memory exhaustion kernel: vmwgfx: NULL pointer dereference in vmw_cmd_dx_define_query kernel: integer overflow in l2cap_config_req() in net/bluetooth/l2cap_core.c kernel: i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() kernel: Bluetooth: L2CAP: Fix u8 overflow kernel: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() kernel: tracing: Fix sleeping function called from invalid context on RT kernel kernel: net: mdio: unexport __init-annotated mdio_bus_init() kernel: arm64: ftrace: consistently handle PLTs. kernel: mm/uffd: fix pte marker when fork() without fork event kernel: Bluetooth: Fix a buffer overflow in mgmt_mesh_add() kernel: tty: n_gsm: add sanity check for gsm-&amp;gt;receive in gsm_receive_buf() kernel: ftrace: Fix NULL pointer dereference in is_ftrace_trampoline when ftrace is dead kernel: tee: add overflow check in register_shm_helper() kernel: tty: n_gsm: fix deadlock and link starvation in outgoing data path kernel: PM: hibernate: defer device probing when resuming from hibernation kernel: ext4: don&amp;#39;t allow journal inode to have encrypt flag kernel: ext4: fix delayed allocation bug in ext4_clu_mapped for bigalloc + inline kernel: erofs: fix order &amp;gt;= MAX_ORDER warning due to crafted negative i_size kernel: perf/x86/intel/uncore: F…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/rhsa-2024:2394</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:0278-1 — Security update for the Linux Kernel</title>
      <link>https://db.gcve.eu/vuln/suse-su-2026:0278-1</link>
      <description>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for the Linux Kernel&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/suse-su-2026:0278-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2023-54137</title>
      <link>https://db.gcve.eu/vuln/ubuntu-cve-2023-54137</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 116 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vfio/type1: fix cap_migration information leak Fix an information leak where an uninitialized hole in struct vfio_iommu_type1_info_cap_migration on the stack is exposed to userspace. The definition of struct vfio_iommu_type1_info_cap_migration contains a hole as shown in this pahole(1) output:   struct vfio_iommu_type1_info_cap_migration {           struct vfio_info_cap_header header;              /*     0     8 */           __u32                      flags;                /*     8     4 */           /* XXX 4 bytes hole, try to pack */           __u64                      pgsize_bitmap;        /*    16     8 */           __u64                      max_dirty_bitmap_size; /*    24     8 */           /* size: 32, cachelines: 1, members: 4 */           /* sum members: 28, holes: 1, sum holes: 4 */           /* last cacheline: 32 bytes */   }; The cap_mig variable is filled in without initializing the hole:   static int vfio_iommu_migration_build_caps(struct vfio_iommu *iommu,                          struct vfio_info_cap *caps)   {       struct vfio_iommu_type1_info_cap_migration cap_mig;       cap_mig.header.id = VFIO_IOMMU_TYPE1_INFO_CAP_MIGRATION;       cap_mig.header.version = 1;       cap_mig.flags = 0;       /* support minimum pgsize */       cap_mig.pgsize_bitmap = (size_t)1 &amp;lt;&amp;lt; __ffs(iommu-&amp;gt;pgsize_bitmap);       cap_mig.max_dirty_bitmap_size = DIRTY_BITMAP_SIZE_MAX;       return vfio_info_add_capability(c…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 116 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: vfio/type1: fix cap_migration information leak Fix an information leak where an uninitialized hole in struct vfio_iommu_type1_info_cap_migration on the stack is exposed to userspace. The definition of struct vfio_iommu_type1_info_cap_migration contains a hole as shown in this pahole(1) output:   struct vfio_iommu_type1_info_cap_migration {           struct vfio_info_cap_header header;              /*     0     8 */           __u32                      flags;                /*     8     4 */           /* XXX 4 bytes hole, try to pack */           __u64                      pgsize_bitmap;        /*    16     8 */           __u64                      max_dirty_bitmap_size; /*    24     8 */           /* size: 32, cachelines: 1, members: 4 */           /* sum members: 28, holes: 1, sum holes: 4 */           /* last cacheline: 32 bytes */   }; The cap_mig variable is filled in without initializing the hole:   static int vfio_iommu_migration_build_caps(struct vfio_iommu *iommu,                          struct vfio_info_cap *caps)   {       struct vfio_iommu_type1_info_cap_migration cap_mig;       cap_mig.header.id = VFIO_IOMMU_TYPE1_INFO_CAP_MIGRATION;       cap_mig.header.version = 1;       cap_mig.flags = 0;       /* support minimum pgsize */       cap_mig.pgsize_bitmap = (size_t)1 &amp;lt;&amp;lt; __ffs(iommu-&amp;gt;pgsize_bitmap);       cap_mig.max_dirty_bitmap_size = DIRTY_BITMAP_SIZE_MAX;       return vfio_info_add_capability(c…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ubuntu-cve-2023-54137</guid>
    </item>
    <item>
      <title>WID-SEC-W-2025-2929 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2025-2929</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um nicht näher spezifizierte Angriffe durchzuführen, die möglicherweise zu einer Denial-of-Service- Bedingung führen oder eine Speicherbeschädigung verursachen können.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2025-2929</guid>
    </item>
  </channel>
</rss>
