46 results · Clear filters · Feed
-
Medium 6.0
An out-of-bounds read vulnerability in the IOMMU could allow a malicious guest to corrupt hypervisor (HV) pages and pot…
-
Medium 5.9
Improper validation of consistency within input in AMD SEV (Secure Encrypted Virtualization) firmware could allow an at…
-
Medium 6.9
Insufficient parameter sanitization in AMD Secure Processor (ASP) TEE DrvSys could allow an attacker with local access …
-
Medium 6.8CVE-2026-0101 Public exploit
Improper validation of specified quantities in input within AMD Power Management Firmware (PMFW) could allow a local at…
-
Medium 5.7
A transient execution vulnerability in some AMD processors may allow an attacker with the ability to execute code on th…
-
Medium 5.9
Improper access control on an internal debug interface could allow a high privileged attacker to bypass memory access c…
-
Medium 6.9
Insufficient parameter sanitization in the AMD Secure Processor (ASP) trusted execution environment (TEE) SPDM driver c…
-
Medium 4.6
Missing Lock Bit Protection in the Northbridge IO (NBIO) could allow a privileged attacker to use an intentionally disa…
-
Medium 6.8
Operation on a resource after expiration or release in the Secure Encrypted Virtualization (SEV) firmware could allow a…
-
Medium 6.0
Incorrect usage of seeds in pseudo-random number generator in the Secure Encrypted Virtualization (SEV) firmware could …
-
Medium 6.0
Operation on a resource after expiration or release in the AMD Secure Encrypted Virtualization (SEV) firmware could all…
-
Medium 4.6
An out-of-bounds write in the AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to …
-
Medium 6.0
Missing Authentication for Critical Function in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malici…
-
Medium 5.9
Improper enforcement of behavioral workflow in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicio…
-
Medium 5.9
Improper Access Control Applied to Mirrored or Aliased Memory Regions in AMD Secure Encrypted Virtualization (SEV) firm…
-
Medium 4.6
Authentication bypass by spoofing in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervi…
-
Medium 5.9
Improper check for unusual or exceptional conditions in AMD Secure Encrypted Virtualization - Secure Nested Paging (SEV…
-
Medium 5.9
Improper access control in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to byp…
-
Medium 5.9
Unverified ownership in Secure Encrypted Virtualization (SEV) firmware could allow a privileged attacker with access to…
-
Medium 4.0
Improper access control within the AMD Secure Encrypted Virtualization (SEV) firmware could allow an attacker with admi…
-
Medium 5.9
Improper resource reuse in the AMD Secure Encrypted Virtualization (SEV) firmware could allow an attacker with hypervis…
-
Medium 4.0
A time-of-check to time-of-use (TOCTOU) race condition in the AMD SEV Secure Encrypted Virtualization (SEV) firmware co…
-
Medium 5.9
Improper handling of overlap between protected memory ranges in the Secure Encrypted Virtualization (SEV) firmware coul…
-
Medium 4.0
Improper validation of Reverse Map Table (RMP) entries in the Secure Encrypted Virtualization (SEV) firmware could allo…
-
Medium 5.9
Insufficient Granularity of Access Control in AMD Secure Encrypted Virtualization (SEV) firmware could allow an attacke…
-
Medium 5.9
Improper validation of unsafe equivalence in input could allow an attacker with high privileges to reclaim the ring buf…
-
Medium 5.9
Expected behavior violation in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to…
-
Medium 4.0
Improper access control for register interface in the Input-Output Memory Management Unit (IOMMU) could allow a privile…
-
Medium 5.9
Missing lock bit protection for NBIO registers could allow a local admin-privileged attacker to modify MMIO routing con…
-
Medium 5.9
A missing lock verification in AMD Secure Processor (ASP) firmware may permit a locally authenticated attacker with adm…
-
Medium 4.6
Improper input validation in the SMM communications buffer could allow a privileged attacker to perform an out of bound…
-
Medium 4.5
Insufficient or Incomplete Data Removal in Hardware Component in SEV firmware doesn't fully flush IOMMU. This can poten…
-
Medium 4.6
A use after free in the SEV firmware could allow a malicous hypervisor to activate a migrated guest with the SINGLE_SOC…
-
Medium 4.0
Insufficient Granularity of Access Control in SEV firmware can allow a privileged attacker to create a SEV-ES Guest to …
-
Medium 4.8
Improper isolation of shared resources on a system on a chip by a malicious local attacker with high privileges could p…
-
Medium 5.3
Improper bound check within AMD CPU microcode can allow a malicious guest to write to host memory, potentially resultin…
-
Medium 6.8
Improper handling of overlap between the segmented reverse map table (RMP) and system management mode (SMM) memory coul…
-
Medium 6.9
Improper access control in secure encrypted virtualization (SEV) could allow a privileged attacker to write to the reve…
-
Medium 5.9
Improper Initialization within the AMD Secure Encrypted Virtualization (SEV) firmware can allow an admin privileged att…
-
Medium 6.7
Improper Prevention of Lock Bit Modification in SEV firmware could allow a privileged attacker to downgrade firmware po…