Sandboxed-containers: kernel: systemd-gpt-auto-generator: guest data leakage in confidential computing (sandboxed containers)
Products / packages Red Hat Enterprise Linux 10 · Red Hat Enterprise Linux 6 · Red Hat Enterprise Linux 7 · 4 more
Published
Severity and exploitation
KEV coverage does not rule out exploitation.
Assessment vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:NSeverity
high7.9CVSS measures technical severity, not the likelihood of an attack.
Known exploitation
Not listed in the checked CISA KEV catalog
Absence from CISA KEV does not rule out attacks.
Public exploit
Not established by this record
Missing evidence does not mean no public exploit exists.
Remediation
Source guidance available
Review the recorded instructions. Guidance may be a workaround rather than a fixed version.
What this means
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…
Source excerpt · redhatAttack conditions
No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.
Review supporting sources →Affected versions
Check the exact model, release, and any platform requirements against your installation.
Red Hat · redhat
Red Hat Enterprise Linux 10
0 ranges
Red Hat · redhat
Red Hat Enterprise Linux 10
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: affected
Product identifiers (CPE)
cpe:/a:redhat:enterprise_linux:10Red Hat · redhat
Red Hat Enterprise Linux 6
0 ranges
Red Hat · redhat
Red Hat Enterprise Linux 6
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: affected
Product identifiers (CPE)
cpe:/o:redhat:rhel_els:6Red Hat · redhat
Red Hat Enterprise Linux 7
0 ranges
Red Hat · redhat
Red Hat Enterprise Linux 7
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: affected
Product identifiers (CPE)
cpe:/o:redhat:rhel_els:7Red Hat · redhat
Red Hat Enterprise Linux 7
0 ranges
Red Hat · redhat
Red Hat Enterprise Linux 7
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: affected
Product identifiers (CPE)
cpe:/o:redhat:rhel_els:7Red Hat · redhat
Red Hat Enterprise Linux 8
0 ranges
Red Hat · redhat
Red Hat Enterprise Linux 8
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: affected
Product identifiers (CPE)
cpe:/a:redhat:enterprise_linux:8Red Hat · redhat
Red Hat Enterprise Linux 8
0 ranges
Red Hat · redhat
Red Hat Enterprise Linux 8
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: affected
Product identifiers (CPE)
cpe:/a:redhat:enterprise_linux:8Red Hat · redhat
Red Hat Enterprise Linux 9
0 ranges
Red Hat · redhat
Red Hat Enterprise Linux 9
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: affected
Product identifiers (CPE)
cpe:/a:redhat:enterprise_linux:9Red Hat · redhat
Red Hat Enterprise Linux 9
0 ranges
Red Hat · redhat
Red Hat Enterprise Linux 9
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: affected
Product identifiers (CPE)
cpe:/a:redhat:enterprise_linux:9Red Hat · redhat
Red Hat OpenShift Container Platform 4
0 ranges
Red Hat · redhat
Red Hat OpenShift Container Platform 4
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: affected
Product identifiers (CPE)
cpe:/a:redhat:openshift:4Red Hat · redhat
Red Hat OpenShift Container Platform 4
0 ranges
Red Hat · redhat
Red Hat OpenShift Container Platform 4
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: affected
Product identifiers (CPE)
cpe:/a:redhat:openshift:4Red Hat · redhat
Red Hat OpenShift Container Platform 5
0 ranges
Red Hat · redhat
Red Hat OpenShift Container Platform 5
Compare with this publisher’s ranges. This does not inspect your installation.
Other versions: affected
Product identifiers (CPE)
cpe:/a:redhat:openshift:5What to do
Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.
Add systemd.gpt_auto=0 to the measured kernel command line (UKI addon) to completely disable systemd-gpt-auto-generator. Since the PodVM already uses explicit partition layout and dm-verity, auto-discovery is unnecessary.
The patches released are using the following mitigation: systemd.image_policy=root=open.
Alternative mitigations:
- Disable swap specifically: add systemd.swap=0 to the kernel command line
- Mask the generator in the guest image: ln -sf /dev/null /etc/systemd/system-generators/systemd-gpt-auto-generator
- Include PCR 5 in the PodVM measurement script alongside PCRs 3, 9, 11, 12
- For systemd 254+: set restrictive image policy via systemd.image_policy=root=verity+signed+encrypted+unprotected+absent:swap=absent:home=absent:srv=absent:var=absent:tmp=absent
cve.new guidance unless attributed to a publisher. This page does not inspect your installation.
Public exploit evidence
No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.
Original source description
Read the full publisher description
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).
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.
References
2 sourcesInside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-121876View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Contributing organizations · 1
Assigning organization
Timeline
All times UTCAdvisory published
Publication date supplied by the source.
Source updated
Latest modification date supplied by the source.
Last imported by cve.new
Latest catalog import, not the date we first saw this advisory.
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.