Guests can trigger NIC interface reset/abort/crash via netback It is possible for a guest to trigger a NIC interface reset/abort/crash in a Linux based network backend by sending certain kinds of packets. It appears to be an (unwritten?) assumption in the rest of the Linux network stack that packet protocol headers are all contained within the linear section of the SKB and some NICs behave badly if this is not the case. This has been reported to occur with Cisco (enic) and Broadcom NetXtrem II BCM5780 (bnx2x) though it may be an issue with other NICs/drivers as well. In case the frontend is sending requests with split headers, netback will forward those violating above mentioned assumption to the networking core, resulting in said misbehavior.
The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Linux_kernel | Linux | 3.19 (including) | 4.9.336 (excluding) |
| Linux_kernel | Linux | 4.10 (including) | 4.14.302 (excluding) |
| Linux_kernel | Linux | 4.15 (including) | 4.19.269 (excluding) |
| Linux_kernel | Linux | 4.20 (including) | 5.4.227 (excluding) |
| Linux_kernel | Linux | 5.5 (including) | 5.10.159 (excluding) |
| Linux_kernel | Linux | 5.11 (including) | 5.15.83 (excluding) |
| Linux_kernel | Linux | 5.16 (including) | 6.0.13 (excluding) |