tls: stop recv() if initial process_rx_list gave us non-DATA
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 692d7b5d1f9125a1cf0595e979e3b5fb7210547e · < a4ed943882a8fc057ea5a67643314245e048bbdd| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
tls: stop recv() if initial process_rx_list gave us non-DATA
If we have a non-DATA record on the rx_list and another record of the same type still on the queue, we will end up merging them: - process_rx_list copies the non-DATA record - we start the loop and process the first available record since it's of the same type - we break out of the loop since the record was not DATA
Just check the record type and jump to the end in case process_rx_list did some work.
From the CVE record · Linux
The Linux kernel TLS receive path can merge two non-DATA records when one is on the receive list and another of the same type remains queued. The input does not establish what an attacker can achieve or whether network access, authentication, or user interaction is required.
Engineers running Linux kernels should check their exposure; affected versions were not provided.