CVE-2026-10656: memory-safety in zephyrproject zephyr
The MAX32xxx USB device controller driver (drivers/usb/udc/udc_max32.c, compatible adi_max32_usbhs) dereferenced an endpoint buffer in its OUT and IN transfer-completion handlers without checking it for NULL. udc_event_xfer_out_done() called net_buf_add(buf, ep_request->actlen) immediately after buf = udc_buf_get(ep_cfg), where udc_buf_get() returns NULL when the endpoint FIFO is empty. A transfer-completion event is queued from interrupt context and processed asynchronously by the driver thread; between queuing and processing, the endpoint FIFO can be drained by host-controlled control flow — in particular udc_setup_received() drains the EP0 OUT/IN FIFOs whenever a new SETUP packet arrives, and dequeue/disable/purge paths drain it likewise. A USB host that aborts an in-flight EP0 control transfer with a new SETUP packet (legal USB behavior) can therefore cause a stale XFER_OUT_DONE event to be processed against an empty FIFO, producing net_buf_add(NULL, ...), a near-NULL pointer dereference that faults and crashes the device. No authentication is required; the attacker is the USB host the device is connected to (physical bus access). Impact is denial of service (device crash). The defect was introduced when the MAX32 UDC driver was added and shipped in Zephyr v4.4.0. The fix adds NULL-buffer checks that return early with UDC_EVT_ERROR/-ENOBUFS in both the OUT-done and IN-done handlers.
AI Analysis
Technical Summary
The MAX32xxx USB device controller driver (drivers/usb/udc/udc_max32.c) in Zephyr OS dereferences an endpoint buffer pointer without checking for NULL in its transfer-completion handlers. Specifically, udc_event_xfer_out_done() calls net_buf_add(buf, ep_request->actlen) immediately after buf = udc_buf_get(ep_cfg), but udc_buf_get() can return NULL if the endpoint FIFO is empty. A USB host can legally abort an in-flight EP0 control transfer by sending a new SETUP packet, which drains the FIFO and causes a stale transfer-completion event to be processed against an empty FIFO, resulting in a near-NULL pointer dereference and device crash. This vulnerability leads to denial of service and requires physical USB bus access. The defect was introduced in Zephyr v4.4.0 when the MAX32 UDC driver was added. The fix involves adding NULL-buffer checks that return early with an error code in the OUT-done and IN-done handlers.
Potential Impact
The vulnerability allows a USB host connected to the device to cause a denial of service by crashing the device through a NULL pointer dereference in the USB device controller driver. There is no impact on confidentiality or integrity, only availability is affected. No authentication is required beyond physical USB connection.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The fix described adds NULL-buffer checks in the transfer-completion handlers to prevent NULL pointer dereference. Until an official patch or update is available, devices should consider restricting physical USB host access or monitoring for abnormal USB control transfer behavior to mitigate risk.
CVE-2026-10656: memory-safety in zephyrproject zephyr
Description
The MAX32xxx USB device controller driver (drivers/usb/udc/udc_max32.c, compatible adi_max32_usbhs) dereferenced an endpoint buffer in its OUT and IN transfer-completion handlers without checking it for NULL. udc_event_xfer_out_done() called net_buf_add(buf, ep_request->actlen) immediately after buf = udc_buf_get(ep_cfg), where udc_buf_get() returns NULL when the endpoint FIFO is empty. A transfer-completion event is queued from interrupt context and processed asynchronously by the driver thread; between queuing and processing, the endpoint FIFO can be drained by host-controlled control flow — in particular udc_setup_received() drains the EP0 OUT/IN FIFOs whenever a new SETUP packet arrives, and dequeue/disable/purge paths drain it likewise. A USB host that aborts an in-flight EP0 control transfer with a new SETUP packet (legal USB behavior) can therefore cause a stale XFER_OUT_DONE event to be processed against an empty FIFO, producing net_buf_add(NULL, ...), a near-NULL pointer dereference that faults and crashes the device. No authentication is required; the attacker is the USB host the device is connected to (physical bus access). Impact is denial of service (device crash). The defect was introduced when the MAX32 UDC driver was added and shipped in Zephyr v4.4.0. The fix adds NULL-buffer checks that return early with UDC_EVT_ERROR/-ENOBUFS in both the OUT-done and IN-done handlers.
CVSS v3.1
Score 4.6medium
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The MAX32xxx USB device controller driver (drivers/usb/udc/udc_max32.c) in Zephyr OS dereferences an endpoint buffer pointer without checking for NULL in its transfer-completion handlers. Specifically, udc_event_xfer_out_done() calls net_buf_add(buf, ep_request->actlen) immediately after buf = udc_buf_get(ep_cfg), but udc_buf_get() can return NULL if the endpoint FIFO is empty. A USB host can legally abort an in-flight EP0 control transfer by sending a new SETUP packet, which drains the FIFO and causes a stale transfer-completion event to be processed against an empty FIFO, resulting in a near-NULL pointer dereference and device crash. This vulnerability leads to denial of service and requires physical USB bus access. The defect was introduced in Zephyr v4.4.0 when the MAX32 UDC driver was added. The fix involves adding NULL-buffer checks that return early with an error code in the OUT-done and IN-done handlers.
Potential Impact
The vulnerability allows a USB host connected to the device to cause a denial of service by crashing the device through a NULL pointer dereference in the USB device controller driver. There is no impact on confidentiality or integrity, only availability is affected. No authentication is required beyond physical USB connection.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The fix described adds NULL-buffer checks in the transfer-completion handlers to prevent NULL pointer dereference. Until an official patch or update is available, devices should consider restricting physical USB host access or monitoring for abnormal USB control transfer behavior to mitigate risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- zephyr
- Date Reserved
- 2026-06-02T15:24:30.893Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4ae01927e9c79719f4564f
Added to database: 07/05/2026, 22:52:09 UTC
Last enriched: 07/20/2026, 19:09:50 UTC
Last updated: 08/19/2026, 10:57:07 UTC
Views: 127
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.