esp: fix skb leak with espintcp and async crypto
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 · < 88d386243ed374ac969dabd3bbc1409a31d81818| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
esp: fix skb leak with espintcp and async crypto
When the TX queue for espintcp is full, esp_output_tail_tcp will return an error and not free the skb, because with synchronous crypto, the common xfrm output code will drop the packet for us.
With async crypto (esp_output_done), we need to drop the skb when esp_output_tail_tcp returns an error.
From the CVE record · Linux
The Linux kernel can leak a packet buffer when espintcp's transmit queue is full and asynchronous crypto causes esp_output_tail_tcp to return an error. An attacker who can trigger this condition could cause packet buffers to leak; the input does not establish whether access is network or local, or whether authentication or user interaction is required.
Operators running the Linux kernel with espintcp and asynchronous crypto should check their systems; affected versions are not specified.