Supraja Sridhara

Name of the Vulnerable Software and Affected Versions: Gramine versions prior to a390e33e16ed374a40de2344562a937f289be2e1 Description: The issue is related to an interface vulnerability due to mismatching software signals versus hardware exceptions. This occurs because the software signals do not properly match the hardware exceptions, leading to a vulnerability. Recommendations: For Gramine versions prior to a390e33e16ed374a40de2344562a937f289be2e1, consider updating to a version that includes the necessary fixes to address the interface vulnerability. As a temporary workaround, review and adjust the signal handling mechanisms to ensure proper matching of software signals with hardware exceptions. However, since the exact fix version is not specified, the best course of action would be to wait for an official update from the developers. At the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: Fortanix Enclave OS version 3.36.1941-EM Description: The issue is related to an interface vulnerability that leads to state corruption via injected signals. Recommendations: For Fortanix Enclave OS version 3.36.1941-EM, at the moment, there is no information about a newer version that contains a fix for this vulnerability.

Name of the Vulnerable Software and Affected Versions: Scontain SCONE version 5.8.0 Description: The issue is related to an interface vulnerability that can cause state corruption through injected signals. Recommendations: For Scontain SCONE version 5.8.0, at the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Linux kernel versions prior to 6.6.7 **Description** An untrusted VMM can trigger int80 syscall handling at any given point in the Linux kernel. This issue is related to the files arch/x86/coco/tdx/tdx.c and arch/x86/mm/mem encrypt amd.c, specifically affecting 32-bit emulation for TDX and SEV. The vulnerability opens the guest OS to manipulation from the VMM side. **Recommendations** For Linux kernel versions prior to 6.6.7, update to version 6.6.7 or later to resolve the issue. As a temporary workaround, consider restricting access to the `int80` syscall handling mechanism until a patch is available. Additionally, restricting the use of 32-bit emulation for TDX and SEV may help minimize the risk of exploitation.

Name of the Vulnerable Software and Affected Versions: Linux kernel versions prior to 6.9 Description: The issue is related to the implementation of the SEV-SNP and SEV-ES mechanisms in the Linux kernel. An untrusted hypervisor can inject virtual interrupt 29 (#VC) at any point in time and trigger its handler, potentially affecting the confidentiality and integrity of protected information. This can be done by injecting a virtual interrupt, which can have an impact on the system's security. Recommendations: For Linux kernel versions prior to 6.9, consider disabling the virtual interrupt 29 (#VC) handler as a temporary workaround until a patch is available. Restrict access to the SEV-SNP and SEV-ES mechanisms to minimize the risk of exploitation. Update to a version of the Linux kernel that is 6.9 or later to fully resolve the issue.

Name of the Vulnerable Software and Affected Versions: Linux kernel versions prior to 6.9 Description: The issue is related to the implementation of the SEV-SNP and SEV-ES protective mechanisms in the Linux kernel, which can be exploited by an untrusted hypervisor to inject virtual interrupts and trigger the SIGFPE signal handler in userspace applications. This can potentially impact the confidentiality and integrity of protected information. An estimated number of affected devices is not provided, and there is no information about real-world incidents where this issue was exploited. Recommendations: For Linux kernel versions prior to 6.9, update to a version that includes the fix for this issue to prevent potential exploitation. As a temporary workaround, consider restricting access to the SIGFPE signal handler in userspace applications until a patch is available.