net: ethernet: lantiq_etop: fix memory disclosure
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 504d4721ee8e432af4b5f196a08af38bc4dac5fe · < e66e38d07b31e177ca430758ed97fbc79f27d966| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: ethernet: lantiq_etop: fix memory disclosure
When applying padding, the buffer is not zeroed, which results in memory disclosure. The mentioned data is observed on the wire. This patch uses skb_put_padto() to pad Ethernet frames properly. The mentioned function zeroes the expanded buffer.
In case the packet cannot be padded it is silently dropped. Statistics are also not incremented. This driver does not support statistics in the old 32-bit format or the new 64-bit format. These will be added in the future. In its current form, the patch should be easily backported to stable versions.
Ethernet MACs on Amazon-SE and Danube cannot do padding of the packets in hardware, so software padding must be applied.
From the CVE record · Linux
The Linux kernel’s lantiq_etop driver does not zero a buffer when padding Ethernet frames in software. On Amazon-SE and Danube Ethernet MACs, which cannot pad frames in hardware, this can expose kernel memory on the wire. The input does not specify whether authentication or user interaction is needed.
Engineers running Linux kernels with the lantiq_etop driver on Amazon-SE or Danube hardware should check their kernel versions against the vendor advisory; affected versions are not specified.