mlx5: fix skb leak while fifo resync and push
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 |
|
|
6.1.186.2.56.3In the Linux kernel, the following vulnerability has been resolved:
mlx5: fix skb leak while fifo resync and push
During ptp resync operation SKBs were poped from the fifo but were never freed neither by napi_consume nor by dev_kfree_skb_any. Add call to napi_consume_skb to properly free SKBs.
Another leak was happening because mlx5e_skb_fifo_has_room() had an error in the check. Comparing free running counters works well unless C promotes the types to something wider than the counter. In this case counters are u16 but the result of the substraction is promouted to int and it causes wrong result (negative value) of the check when producer have already overlapped but consumer haven't yet. Explicit cast to u16 fixes the issue.
From the CVE record · Linux
The Linux kernel's mlx5 driver can leak socket buffers (SKBs) during PTP FIFO resynchronization because popped buffers are not freed. A separate FIFO room-check error can also cause an SKB leak when its counters wrap. The input does not establish an attacker path, authentication requirement, or user interaction requirement.
Engineers running Linux kernels with the mlx5 driver should check their deployments; affected versions are not specified.