net: ll_temac: Make sure to free skb when it is completely used
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: ll_temac: Make sure to free skb when it is completely used
With the skb pointer piggy-backed on the TX BD, we have a simple and efficient way to free the skb buffer when the frame has been transmitted. But in order to avoid freeing the skb while there are still fragments from the skb in use, we need to piggy-back on the TX BD of the skb, not the first.
Without this, we are doing use-after-free on the DMA side, when the first BD of a multi TX BD packet is seen as completed in xmit_done, and the remaining BDs are still being processed.
From the CVE record · Linux
The Linux kernel’s ll_temac driver can free a packet buffer while DMA is still processing parts of a packet that uses multiple transmit buffer descriptors. This can cause a DMA-side use-after-free when the first descriptor completes; the input does not specify how an attacker could trigger it or whether authentication or user interaction is required.
Engineers running Linux kernels with the ll_temac driver should check their versions; affected versions are not specified.