CVE-2026-129808 in SOES
Summary
by MITRE • 11/21/2026
The EoE receive and transmit paths call the handle_recv_buffer and fetch_send_buffer 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 when the transmit polling loop runs.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability described involves a critical null pointer dereference within the Ethernet over USB (EoE) subsystem of the Linux kernel, specifically affecting both receive and transmit data paths. This flaw stems from an implementation oversight where the code attempts to invoke function pointers for buffer handling without verifying their initialization status first. In systems utilizing this framework, applications are permitted to define optional callbacks named handle_recv_buffer and fetch_send_buffer to manage custom memory allocation or processing logic for incoming and outgoing network frames respectively. While these interfaces provide flexibility for specialized use cases such as zero-copy networking or hardware-specific optimizations, the kernel code fails to perform a sanity check before dereferencing these pointers during normal operation.
When an application registers with the EoE subsystem but omits the definition of either callback, the corresponding function pointer remains uninitialized and defaults to NULL within the kernel's internal structures. The operational impact manifests immediately upon network activity. For the receive path, as soon as the first Ethernet frame arrives from the USB device, the system attempts to call handle_recv_buffer through this null reference. Similarly, in the transmit direction, when the periodic polling loop executes to check for pending data to send, it triggers fetch_send_buffer via a NULL pointer. This results in an immediate kernel panic or crash due to an invalid memory access at address zero, effectively causing a denial of service condition that disrupts network connectivity and potentially destabilizes the entire host system depending on the configured fault handling policies.
From a technical classification perspective, this vulnerability aligns with CWE-476, which denotes NULL Pointer Dereference. The root cause is a failure to validate input parameters or internal state before execution, specifically neglecting to check if optional function pointers have been properly assigned by the calling application layer. This type of error is particularly dangerous in kernel space because it bypasses user-space protections and directly compromises system stability. In terms of adversarial tactics, this flaw could be leveraged for local denial-of-service attacks under MITRE ATT&CK technique T1499, specifically Endpoint Denial of Service via resource exhaustion or crash induction. An attacker with the ability to load a malicious kernel module or interact with the EoE device interface can trigger these code paths simply by initiating network traffic without providing the expected callback implementations.
Mitigation strategies for this vulnerability require both immediate patching and long-term defensive coding practices. The primary remediation is to apply vendor-provided security updates that introduce explicit NULL checks before invoking handle_recv_buffer and fetch_send_buffer. If a pointer is found to be null, the kernel should either fall back to default buffer handling mechanisms or return an appropriate error code rather than proceeding with the dereference operation. For developers integrating EoE functionality, it is crucial to ensure that all required callbacks are defined even if they perform minimal operations, thereby guaranteeing non-null pointers at runtime. Additionally, enabling kernel hardening features such as KASAN (Kernel Address Sanitizer) during development can help detect these types of memory safety violations early in the software lifecycle before deployment.