13 matches found
EUVD-2026-132163
When the last EoE fragment has the TIMEAPPEND flag set, the handler subtracts 4 from rxframeoffset to strip the timestamp. There is no check that rxframeoffset is at least 4. A fragment carrying fewer than 4 bytes of payload that is also marked LAST causes rxframeoffset to wrap to 0xFFFFFFFC, whi...
EUVD-2026-132164
The EoE fragment reassembly code uses a frame size from the wire as the bound for memcpy into the application receive buffer, without checking that the declared size fits in the actual buffer. A master can write up to 2016 bytes into a buffer the application may have sized much smaller...
CVE-2026-129808
The EoE receive and transmit paths call the handlerecvbuffer and fetchsendbuffer callbacks without first checking whether they are set. Both callbacks are documented as optional; an application that omits either one causes a call through a NULL function pointer when the first EoE frame arrives or...
CVE-2026-129795
When the last EoE fragment has the TIMEAPPEND flag set, the handler subtracts 4 from rxframeoffset to strip the timestamp. There is no check that rxframeoffset is at least 4. A fragment carrying fewer than 4 bytes of payload that is also marked LAST causes rxframeoffset to wrap to 0xFFFFFFFC, whi...
CVE-2026-129794
The EoE fragment reassembly code uses a frame size from the wire as the bound for memcpy into the application receive buffer, without checking that the declared size fits in the actual buffer. A master can write up to 2016 bytes into a buffer the application may have sized much smaller...
CVE-2026-129808
The EoE (Ethernet over Ethernet) receive and transmit paths are vulnerable to a NULL pointer dereference because the handle_recv_buffer and fetch_send_buffer callbacks are invoked without verification. Since these callbacks are optional , applications that omit them will trigger a call through a ...
CVE-2026-129808 EoE Buffer Callback NULL Pointer Dereference
The EoE receive and transmit paths call the handlerecvbuffer and fetchsendbuffer callbacks without first checking whether they are set. Both callbacks are documented as optional; an application that omits either one causes a call through a NULL function pointer when the first EoE frame arrives or...
CVE-2026-129802 EoE Set-IP Out-of-Bounds Reads Before Bounds Check
EOEsetip reads each network parameter field MAC, IP, subnet, gateway, DNS IP, DNS name from the mailbox payload before checking whether the payload is large enough to contain them. The single bounds check at the end of the function does not prevent the reads from happening. A master can send a...
CVE-2026-129802
The EOE_set_ip function is vulnerable to out-of-bounds reads because it retrieves network parameters—including MAC, IP, subnet, gateway, DNS IP, and DNS name—from a mailbox payload before verifying if the payload is sufficiently large. A master can trigger this by sending a Set-IP frame with all ...
CVE-2026-129795
The EoE Timestamp-Strip Integer Underflow vulnerability occurs when the last EoE fragment has the TIME_APPEND flag set. The handler subtracts 4 from rxframeoffset to strip the timestamp without verifying that rxframeoffset is at least 4. If a fragment with fewer than 4 bytes of payload is marked ...
CVE-2026-129795 EoE Timestamp-Strip Integer Underflow
When the last EoE fragment has the TIMEAPPEND flag set, the handler subtracts 4 from rxframeoffset to strip the timestamp. There is no check that rxframeoffset is at least 4. A fragment carrying fewer than 4 bytes of payload that is also marked LAST causes rxframeoffset to wrap to 0xFFFFFFFC, whi...
CVE-2026-129794
The EoE fragment reassembly code contains an Out-of-bounds Write vulnerability (CWE-787). The software fails to verify that the frame size received from the wire fits within the application receive buffer before performing a memcpy operation. This allows a master to write up to 2016 bytes into a ...
CVE-2026-129794 EoE Fragment Reassembly Heap Out-of-Bounds Write
The EoE fragment reassembly code uses a frame size from the wire as the bound for memcpy into the application receive buffer, without checking that the declared size fits in the actual buffer. A master can write up to 2016 bytes into a buffer the application may have sized much smaller...