Błąd w obsłudze zerowych rekordów w jądrze Linux może prowadzić do nieprawidłowego przetwarzania danych, co stwarza ryzyko wycieku informacji.

CVSS 3.1

9,8 · [email protected]

Wektor CVSS

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

2,88 % · model z 2026-10-19

Polityka rekomendacji

action-2026-10-p1

Przechowywanie

Bieżący rekord

Opis NVD

In the Linux kernel, the following vulnerability has been resolved: tls: fix handling of zero-length records on the rx_list Each recvmsg() call must process either - only contiguous DATA records (any number of them) - one non-DATA record If the next record has different type than what has already been processed we break out of the main processing loop. If the record has already been decrypted (which may be the case for TLS 1.3 where we don't know type until decryption) we queue the pending record to the rx_list. Next recvmsg() will pick it up from there. Queuing the skb to rx_list after zero-copy decrypt is not possible, since in that case we decrypted directly to the user space buffer, and we don't have an skb to queue (darg.skb points to the ciphertext skb for access to metadata like length). Only data records are allowed zero-copy, and we break the processing loop after each non-data record. So we should never zero-copy and then find out that the record type has changed. The corner case we missed is when the initial record comes from rx_list, and it's zero length.

EPSS opisuje prognozowane prawdopodobieństwo zaobserwowania wykorzystania w ciągu kolejnych 30 dni. Nie jest prawdopodobieństwem włamania do Twojego urządzenia.