<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-13T01:23:17.841884+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/fkie_cve-2026-121876</id>
    <title>fkie_cve-2026-121876</title>
    <updated>2026-11-13T01:23:17.843213+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>A flaw was found in the interaction between systemd-gpt-auto-generator and 
confidential computing guest VM images in OpenShift Sandboxed Containers 
(confidential peer pods). systemd-gpt-auto-generator automatically discovers 
and mounts GPT partitions by type GUID at boot with no user confirmation. In 
the confidential computing threat model, where the host/hypervisor is the 
adversary, a malicious host can inject partitions into the guest's virtual 
disk. Most critically, injecting a swap partition causes the guest kernel to 
page out TEE-encrypted memory to a host-controlled block device, breaking the 
confidentiality guarantee of the hardware TEE (AMD SEV-SNP, Intel TDX).</p>
<p>The PodVM images use a GPT-partitioned disk with dm-verity on the root 
partition. However, the roothash= kernel parameter only disables root 
auto-discovery — non-root partitions (swap, /home, /var, /srv, /var/tmp) are 
still auto-discovered and mounted. The generator is shipped unmasked in the 
RHEL systemd-udev subpackage, and no kernel command line parameter in the 
measured UKI addon disables it. Additionally, the PodVM measurement script 
captures PCRs 3, 9, 11, and 12, but not PCR 5 (GPT partition table), so 
partition table modifications are not detected by remote attestation.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-121876"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-pvr5-j3rg-w9p8</id>
    <title>GHSA-pvr5-j3rg-w9p8</title>
    <updated>2026-11-13T01:23:17.843272+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>A flaw was found in the interaction between systemd-gpt-auto-generator and 
confidential computing guest VM images in OpenShift Sandboxed Containers 
(confidential peer pods). systemd-gpt-auto-generator automatically discovers 
and mounts GPT partitions by type GUID at boot with no user confirmation. In 
the confidential computing threat model, where the host/hypervisor is the 
adversary, a malicious host can inject partitions into the guest's virtual 
disk. Most critically, injecting a swap partition causes the guest kernel to 
page out TEE-encrypted memory to a host-controlled block device, breaking the 
confidentiality guarantee of the hardware TEE (AMD SEV-SNP, Intel TDX).</p>
<p>The PodVM images use a GPT-partitioned disk with dm-verity on the root 
partition. However, the roothash= kernel parameter only disables root 
auto-discovery — non-root partitions (swap, /home, /var, /srv, /var/tmp) are 
still auto-discovered and mounted. The generator is shipped unmasked in the 
RHEL systemd-udev subpackage, and no kernel command line parameter in the 
measured UKI addon disables it. Additionally, the PodVM measurement script 
captures PCRs 3, 9, 11, and 12, but not PCR 5 (GPT partition table), so 
partition table modifications are not detected by remote attestation.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-pvr5-j3rg-w9p8"/>
  </entry>
</feed>
