Summary
Ein Angreifer kann mehrere Schwachstellen in AMD Prozessor ausnutzen, um beliebigen Code auszuführen, sich erhöhte Berechtigungen zu verschaffen, Sicherheitsmaßnahmen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, vertrauliche Informationen offenzulegen oder Daten zu manipulieren.
Product
Prozessoren sind die zentralen Rechenwerke eines Computers.
Vulnerabilities 28
-
High 8.7
Improper Access Control in an on-chip debug interface could allow a privileged attacker to enable a debug interface and…
-
High 7.3
A buffer overflow in the AMD Secure Processor (ASP) bootloader could allow an attacker to overwrite memory, potentially…
-
High 7.1
Improper system call parameter validation in the Trusted OS may allow a malicious driver to perform mapping or unmappin…
-
High 7.1
Insufficient granularity of access control in ASP (AMD Secure Processor) may allow an attacker with an untrusted user s…
-
High 7.1
Improper input validation in system management mode (SMM) could allow a privileged attacker to overwrite stack memory l…
-
High 7.0
Improper input validation in the SMM handler could allow an attacker with Ring0 access to write to SMRAM and modify exe…
-
Medium 6.9
Improper Input validation in the AMD Secure Processor (ASP) PCI driver may allow a local attacker to create a buffer ov…
-
Medium 6.9
Improper access control in secure encrypted virtualization (SEV) could allow a privileged attacker to write to the reve…
-
Medium 6.8
Improper handling of overlap between the segmented reverse map table (RMP) and system management mode (SMM) memory coul…
-
Medium 6.7
Improper Prevention of Lock Bit Modification in SEV firmware could allow a privileged attacker to downgrade firmware po…
-
Medium 6.0
Improper restriction of operations within the bounds of a memory buffer in PCIe® Link could allow an attacker with acce…
-
Medium 5.9
Improper input validation in IOMMU could allow a malicious hypervisor to reconfigure IOMMU registers resulting in loss …
-
Medium 5.9
Improper access control in AMD Secure Encrypted Virtualization (SEV) firmware could allow a malicious hypervisor to byp…
-
Medium 5.9
Improper Initialization within the AMD Secure Encrypted Virtualization (SEV) firmware can allow an admin privileged att…
-
Medium 5.4
Insufficient parameter sanitization in AMD Secure Processor (ASP) Boot Loader could allow an attacker with access to SP…
-
Medium 5.3
Improper bound check within AMD CPU microcode can allow a malicious guest to write to host memory, potentially resultin…
-
Medium 4.8
Insufficient input parameter sanitization in AMD Secure Processor (ASP) Boot Loader (legacy recovery mode only) could a…
-
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 4.6
Improper input validation in the SMM communications buffer could allow a privileged attacker to perform an out of bound…
-
Medium 4.6
A Time-of-check time-of-use (TOCTOU) race condition in the SMM communications buffer could allow a privileged attacker …
-
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.6
Insufficient Granularity of Access Control in SEV firmware could allow a privileged user with a malicious hypervisor to…
-
Medium 4.5
Insufficient or Incomplete Data Removal in Hardware Component in SEV firmware doesn't fully flush IOMMU. This can poten…
-
Medium 4.0
Insufficient Granularity of Access Control in SEV firmware can allow a privileged attacker to create a SEV-ES Guest to …
-
Low 1.8
Improper syscall input validation in ASP (AMD Secure Processor) may force the kernel into reading syscall parameter val…
-
Low 1.8
An observable timing discrepancy in the ASP could allow a privileged attacker to perform a brute-force attack against t…
-
Low 1.8
Improper handling of error condition during host-induced faults can allow a local high-privileged attack to selectively…
-
Low 1.8
Missing Checks in certain functions related to RMP initialization can allow a local admin privileged attacker to cause …
Revision history
-
#6
Referenz(en) aufgenommen: EUVD-2023-60597
-
#5
Neue Updates von HP aufgenommen
-
#4
Referenz(en) aufgenommen: EUVD-2021-34843
-
#3
Referenz(en) aufgenommen: EUVD-2025-209862
-
#2
Neue Updates von Dell aufgenommen
-
#1
Initiale Fassung
References
-
AMD Athlon and AMD Ryzen Processor Vulnerabilities – February 2026 vom 2026-02-10
https://www.amd.com/en/resources/product-security/bulletin/amd-sb-4013.html
-
HP Security Bulletin HPESBHF04999 vom 2026-02-10
https://support.hpe.com/hpesc/public/docDisplay?docId=hpesbhf04999en_us&docLocale=en_US
-
HP Security Bulletin HPSBHF04090 vom 2025-12-05
https://support.hp.com/de-de/document/ish_14067521-14067543-16/HPSBHF04090
-
Lenovo Security Advisory LEN-210698 vom 2026-02-10
https://support.lenovo.com/us/en/product_security/LEN-210698
-
Dell Security Advisory DSA-2026-016 vom 2026-02-10
https://www.dell.com/support/kbdoc/de-de/000398671/dsa-2026-016
-
Dell Security Advisory DSA-2026-026 vom 2026-02-11
https://www.dell.com/support/kbdoc/en-us/000426703/dsa-2026-026-security-update-for-dell-amd-based-poweredge-server-vulnerability
-
HP Security Bulletin HPSBHF04127 vom 2026-06-12
https://support.hp.com/de-de/document/ish_15142748-15143245-16/HPSBHF04127