IOMMU improperly handles certain special address ranges with invalid device table entries (DTEs), which may allow an attacker with privileges and a compromised Hypervisor to induce DTE faults to bypass RMP checks in SEV-SNP, potentially leading to a loss of guest integrity.
Product
debian/amd64-microcode vulnerabilities
37 published CVES affecting debian/amd64-microcode, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 37
- Critical
- 0
- High
- 3
- Medium
- 24
- Low
- 4
- Unscored
- 6
- CISA KEV
- 0
Latest debian/amd64-microcode CVEs
Newest publication first · page 2 of 2
-
MediumCVSS 6.0 EPSS 0.19%
-
HighCVSS 7.5 EPSS 0.63%
Improper validation in a model specific register (MSR) could allow a malicious program with ring0 access to modify SMM configuration while SMI lock is enabled, potentially leading to arbitrary code execution.
-
MediumCVSS 6.5 EPSS 1.0%
Improper or unexpected behavior of the INVD instruction in some AMD CPUs may allow an attacker with a malicious hypervisor to affect cache line write-back behavior of the CPU leading to a potential loss of guest virtual machine (VM) memory integrity.
-
MediumCVSS 4.7 EPSS 7.3%
A side channel vulnerability on some of the AMD CPUs may allow an attacker to influence the return address prediction. This may result in speculative execution at an attacker-controlled address, potentially leading to information disclosure.
-
Unknown
-
Unknown
-
MediumCVSS 5.5 EPSS 5.1%
An issue in “Zen 2” CPUs, under specific microarchitectural circumstances, may allow an attacker to potentially access sensitive information.
-
Unknown
-
Unknown
-
Unknown
-
MediumCVSS 5.3 EPSS 1.6%
Secure Encrypted Virtualization (SEV) on Advanced Micro Devices (AMD) Platform Security Processor (PSP; aka AMD Secure Processor or AMD-SP) 0.17 build 11 and earlier has an insecure cryptographic implementation.
-
MediumCVSS 5.6 EPSS 73.2%
Systems with microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized disclosure of information to an attacker with local user access via a side-channel analysis.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.