CVE-2023-52767

In the Linux kernel, the following vulnerability has been resolved: tls: fix NULL deref on tls_sw_splice_eof() with empty record syzkaller discovered that if tls_sw_splice_eof() is executed as part of sendfile() when the plaintext/ciphertext sk_msg are empty, the send path gets confused because the empty ciphertext buffer does not have enough space for the encryption overhead. This causes tls_push_record() to go on the `split = true` path (which is only supposed to be used when interacting with an attached BPF program), and then get further confused and hit the tls_merge_open_record() path, which then assumes that there must be at least one populated buffer element, leading to a NULL deref. It is possible to have empty plaintext/ciphertext buffers if we previously bailed from tls_sw_sendmsg_locked() via the tls_trim_both_msgs() path. tls_sw_push_pending_record() already handles this case correctly; let's do the same check in tls_sw_splice_eof().
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.7:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.7:rc2:*:*:*:*:*:*

History

06 Jan 2025, 20:29

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/2214e2bb5489145aba944874d0ee1652a0a63dc8 - () https://git.kernel.org/stable/c/2214e2bb5489145aba944874d0ee1652a0a63dc8 - Patch
References () https://git.kernel.org/stable/c/53f2cb491b500897a619ff6abd72f565933760f0 - () https://git.kernel.org/stable/c/53f2cb491b500897a619ff6abd72f565933760f0 - Patch
References () https://git.kernel.org/stable/c/944900fe2736c07288efe2d9394db4d3ca23f2c9 - () https://git.kernel.org/stable/c/944900fe2736c07288efe2d9394db4d3ca23f2c9 - Patch
First Time Linux linux Kernel
Linux
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 5.5
CWE CWE-476
CPE cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.7:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.7:rc2:*:*:*:*:*:*

21 Nov 2024, 08:40

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/2214e2bb5489145aba944874d0ee1652a0a63dc8 - () https://git.kernel.org/stable/c/2214e2bb5489145aba944874d0ee1652a0a63dc8 -
References () https://git.kernel.org/stable/c/53f2cb491b500897a619ff6abd72f565933760f0 - () https://git.kernel.org/stable/c/53f2cb491b500897a619ff6abd72f565933760f0 -
References () https://git.kernel.org/stable/c/944900fe2736c07288efe2d9394db4d3ca23f2c9 - () https://git.kernel.org/stable/c/944900fe2736c07288efe2d9394db4d3ca23f2c9 -
Summary
  • (es) En el kernel de Linux, se resolvió la siguiente vulnerabilidad: tls: corrige NULL deref en tls_sw_splice_eof() con registro vacío syzkaller descubrió que si tls_sw_splice_eof() se ejecuta como parte de sendfile() cuando el texto plano/texto cifrado sk_msg está vacío, el envío La ruta se confunde porque el búfer de texto cifrado vacío no tiene suficiente espacio para la sobrecarga de cifrado. Esto hace que tls_push_record() vaya a la ruta `split = true` (que se supone que solo debe usarse al interactuar con un programa BPF adjunto), y luego se confunda aún más y acceda a la ruta tls_merge_open_record(), que luego supone que hay debe haber al menos un elemento de búfer poblado, lo que lleva a una deref NULL. Es posible tener buffers de texto plano/texto cifrado vacíos si previamente salimos de tls_sw_sendmsg_locked() a través de la ruta tls_trim_both_msgs(). tls_sw_push_pending_record() ya maneja este caso correctamente; hagamos la misma verificación en tls_sw_splice_eof().

21 May 2024, 16:15

Type Values Removed Values Added
New CVE

Information

Published : 2024-05-21 16:15

Updated : 2025-01-06 20:29


NVD link : CVE-2023-52767

Mitre link : CVE-2023-52767

CVE.ORG link : CVE-2023-52767


JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-476

NULL Pointer Dereference