net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ff06ab13a4ccae4acb44a2d4e3ece367b616ab50 · < 2aa8a4fa8d5b7d0e1ebcec100e1a4d80a1f4b21a| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: usb: cdc_ncm: add ndpoffset to NDP16 nframes bounds check
cdc_ncm_rx_verify_ndp16() validates that the NDP header and its DPE entries fit within the skb. The first check correctly accounts for ndpoffset:
if ((ndpoffset + sizeof(struct usb_cdc_ncm_ndp16)) > skb_in->len)
but the second check omits it:
if ((sizeof(struct usb_cdc_ncm_ndp16) + ret * (sizeof(struct usb_cdc_ncm_dpe16))) > skb_in->len)
This validates the DPE array size against the total skb length as if the NDP were at offset 0, rather than at ndpoffset. When the NDP is placed near the end of the NTB (large wNdpIndex), the DPE entries can extend past the skb data buffer even though the check passes. cdc_ncm_rx_fixup() then reads out-of-bounds memory when iterating the DPE array.
Add ndpoffset to the nframes bounds check and use struct_size_t() to express the NDP-plus-DPE-array size more clearly.
From the CVE record · Linux
The Linux kernel’s USB CDC NCM receive path omits the NDP offset from a bounds check on DPE entries. An NTB with its NDP near the end of the buffer can pass the check and cause an out-of-bounds read. The input does not specify attacker access requirements or whether user interaction is needed.
Engineers running Linux kernels with the USB CDC NCM driver should check their exposure; affected versions are not specified.