net/mlx5e: SHAMPO, Fix incorrect page release
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| 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/mlx5e: SHAMPO, Fix incorrect page release
Under the following conditions: 1) No skb created yet 2) header_size == 0 (no SHAMPO header) 3) header_index + 1 % MLX5E_SHAMPO_WQ_HEADER_PER_PAGE == 0 (this is the last page fragment of a SHAMPO header page)
a new skb is formed with a page that is NOT a SHAMPO header page (it is a regular data page). Further down in the same function (mlx5e_handle_rx_cqe_mpwrq_shampo()), a SHAMPO header page from header_index is released. This is wrong and it leads to SHAMPO header pages being released more than once.
From the CVE record · Linux
The Linux kernel’s net/mlx5e SHAMPO receive path can release a SHAMPO header page more than once when no skb has been created, the header size is zero, and processing reaches the last fragment of a SHAMPO header page. The input does not establish whether an attacker can trigger this condition, or specify network or local access, authentication, or user interaction requirements.
Engineers running Linux kernels with the net/mlx5e SHAMPO receive path should check their systems; affected versions are not specified.