net: usb: ax88179_178a: Fix out-of-bounds accesses in RX fixup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e2ca90c276e1fc410d7cd3c1a4eee245ec902a20 · < ffd0393adcdcefab7e131488e10dcfde5e02d6eb| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: usb: ax88179_178a: Fix out-of-bounds accesses in RX fixup
ax88179_rx_fixup() contains several out-of-bounds accesses that can be triggered by a malicious (or defective) USB device, in particular:
- The metadata array (hdr_off..hdr_off+2*pkt_cnt) can be out of bounds, causing OOB reads and (on big-endian systems) OOB endianness flips. - A packet can overlap the metadata array, causing a later OOB endianness flip to corrupt data used by a cloned SKB that has already been handed off into the network stack. - A packet SKB can be constructed whose tail is far beyond its end, causing out-of-bounds heap data to be considered part of the SKB's data.
I have tested that this can be used by a malicious USB device to send a bogus ICMPv6 Echo Request and receive an ICMPv6 Echo Reply in response that contains random kernel heap data. It's probably also possible to get OOB writes from this on a little-endian system somehow - maybe by triggering skb_cow() via IP options processing -, but I haven't tested that.
From the CVE record · Linux
The Linux kernel’s ax88179_178a USB network driver has out-of-bounds accesses in its RX fixup function. A connected malicious USB device can trigger them and cause an ICMPv6 Echo Reply to contain kernel heap data. No authentication or user interaction beyond connecting the device is described.
Engineers running Linux kernels with the ax88179_178a USB network driver should check their exposure; affected versions are not specified.