CVE-2026-0462 describes an insufficient granularity of access control vulnerability in AMD Secure Encrypted Virtualization (SEV) firmware. This flaw could allow a malicious hypervisor to redirect accesses to MMIO memory, potentially compromising the integrity of guest memory. The vulnerability has a medium severity rating with a CVSS score of 5.9. No patch or remediation information is provided, and no known exploits are reported in the wild.
This vulnerability involves incomplete cleanup during VMRUN error handling in Secure Encrypted Virtualization-Secure Nested Paging (SEV-SNP) environments. It could allow unauthorized access to guest register state, potentially leading to information disclosure and confidentiality impacts. The issue has a medium severity rating with a CVSS score of 4.6. No affected versions or patches are specified, and there are no known exploits in the wild.
A vulnerability exists in the SDO Information Get Object Description and Get Entry Description responses where the object or entry name is copied into a mailbox data buffer without sufficient space for a null terminator. This causes the null terminator byte to be written one byte beyond the buffer's end when the name exactly fills the buffer, resulting in a buffer overflow condition.
This vulnerability involves an object dictionary entry that can have write-access flags despite having a NULL data pointer. Specifically, when a constant value is stored directly in the value field rather than in addressable storage, the CoE SDO download handler fails to verify the presence of storage before writing. This results in the handler writing the master-supplied payload through a NULL pointer, causing an availability impact.
This vulnerability involves the CoE entry gate accepting frames with a mailbox header length smaller than required for a normal SDO Download. Specifically, it accepts lengths as low as 8 bytes, while a proper SDO Download requires at least 10 bytes. This discrepancy causes a miscalculation in the segmented-transfer logic due to unsigned integer wrap, resulting in an unchecked declared SDO size. Consequently, the system reads beyond the actual payload boundary, potentially leading to out-of-bounds memory reads.
CVE-2026-129809 is a vulnerability involving a NULL pointer dereference in the ESC_foeprocess handler. This occurs when an incoming mailbox frame is processed before the application has called FOE_config to initialize necessary file table and buffer pointers. If these pointers are NULL, the handler dereferences them, leading to a crash or denial of service.
CVE-2026-129806 describes a vulnerability in the CoE SDO upload handler where a NULL pointer dereference can occur. This happens when the handler processes entries holding a constant in the value field, which have their data set to NULL. A master requesting such an entry triggers the NULL pointer dereference in the upload path, potentially causing a denial of service.
CVE-2026-129801 is a vulnerability in the FoE DATA frame handler where the payload length is derived from a master-supplied mailbox length field without proper bounds checking against the physical mailbox buffer size. This can lead to reading beyond the buffer when a master declares a large length but sends a shorter frame.
CVE-2026-129810 is a vulnerability involving NULL pointer dereferences in the ESC_eoeprocess and ESC_eoeprocess_tx functions. These functions can be invoked before the application initializes the callback table pointer via EOE_config, leading to dereferencing a NULL pointer during processing of incoming EoE frames and transmit polling cycles. This results in a denial of service due to application crashes.
CVE-2026-129808 describes a vulnerability in the EoE receive and transmit paths where optional callback functions handle_recv_buffer and fetch_send_buffer are called without checking if they are set. If an application omits either callback, this results in a call through a NULL function pointer when processing EoE frames or during transmit polling, causing a denial of service.
The vulnerability involves the sizeOfPDO function, which during state transitions uses the subindex-0 count of SM-assign and PDO-mapping objects as loop bounds without validating these counts against the actual descriptor array sizes. If these subindex-0 values are writable via SDO, a malicious master can write a value of 0xFF, causing sizeOfPDO to read beyond the end of the descriptor arrays during the next transition to SAFEOP.
CVE-2026-129807 describes a vulnerability in the FoE file table where entries can omit a write handler by setting write_function to NULL, making the file read-only. The FOE_fopen function did not verify the presence of a write handler before processing write requests, leading to a NULL pointer dereference when a write request (WRQ) was sent for a read-only file.
CVE-2026-129811 is a vulnerability where the PDO mapping bit lengths in mapping objects can be overwritten by a master via SDO. This allows crafting of mappings with total bit counts exceeding the allocated process data buffers, leading to out-of-bounds writes during process data cycles after the PREOP to SAFEOP transition. The flaw can result in high impact including confidentiality, integrity, and availability compromise.
The vulnerability in EOE_set_ip involves reading multiple network parameter fields from a mailbox payload without proper bounds checking before each read. This can lead to out-of-bounds memory reads when a specially crafted Set-IP frame is sent with all flags set and a minimal mailbox header length. The flaw is identified as a medium severity issue with a CVSS score of 4.3.
CVE-2026-129812 is a vulnerability involving an object dictionary entry that holds a constant and has a NULL data pointer. This flaw causes a NULL pointer dereference during process data exchange when such an entry is mapped to a PDO by a master device.
The vulnerability CVE-2026-129804 involves FOE_read and FOE_write functions storing the filename length as a uint8_t, causing truncation modulo 256. This can result in a length of zero under specific conditions, leading FOE_fopen to incorrectly open the first registered file with a password of zero regardless of the requested filename.
CVE-2026-129813 is a vulnerability in the CoE complete-access download handler where it iterates over all subindices of an object and writes a master-supplied payload into each writable entry. The flaw arises because entries holding constants have write-access flags set but contain NULL data pointers, and the handler does not check for NULL pointers before writing. This results in a write through a NULL pointer, causing an availability impact.
A vulnerability exists in the CoE SDO download handler for flexible-length objects such as VISIBLE_STRING and OCTET_STRING. The handler does not verify that the declared transfer size fits within the object before performing writes, affecting the zero-padding memset and the first-frame copy into the object buffer. This can lead to buffer overflows.
A vulnerability exists in the handling of the last EoE fragment when the TIME_APPEND flag is set. The handler subtracts 4 from rxframeoffset to strip a timestamp without verifying that rxframeoffset is at least 4. If a fragment marked LAST carries fewer than 4 bytes of payload, rxframeoffset underflows to 0xFFFFFFFC, which is then used as the buffer length and passed to the TCP/IP stack.
CVE-2026-129798 is a high-severity vulnerability in the CoE SDO segmented download handler where the write pointer advances by each incoming segment's size without tracking the total bytes written. This flaw allows a master device to send multiple non-last segments, causing the pointer to move beyond the end of the object buffer or the complete-access staging buffer.