CVE-2023-52886

In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix race by not overwriting udev->descriptor in hub_port_init() Syzbot reported an out-of-bounds read in sysfs.c:read_descriptors(): BUG: KASAN: slab-out-of-bounds in read_descriptors+0x263/0x280 drivers/usb/core/sysfs.c:883 Read of size 8 at addr ffff88801e78b8c8 by task udevd/5011 CPU: 0 PID: 5011 Comm: udevd Not tainted 6.4.0-rc6-syzkaller-00195-g40f71e7cd3c6 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xd9/0x150 lib/dump_stack.c:106 print_address_description.constprop.0+0x2c/0x3c0 mm/kasan/report.c:351 print_report mm/kasan/report.c:462 [inline] kasan_report+0x11c/0x130 mm/kasan/report.c:572 read_descriptors+0x263/0x280 drivers/usb/core/sysfs.c:883 ... Allocated by task 758: ... __do_kmalloc_node mm/slab_common.c:966 [inline] __kmalloc+0x5e/0x190 mm/slab_common.c:979 kmalloc include/linux/slab.h:563 [inline] kzalloc include/linux/slab.h:680 [inline] usb_get_configuration+0x1f7/0x5170 drivers/usb/core/config.c:887 usb_enumerate_device drivers/usb/core/hub.c:2407 [inline] usb_new_device+0x12b0/0x19d0 drivers/usb/core/hub.c:2545 As analyzed by Khazhy Kumykov, the cause of this bug is a race between read_descriptors() and hub_port_init(): The first routine uses a field in udev->descriptor, not expecting it to change, while the second overwrites it. Prior to commit 45bf39f8df7f ("USB: core: Don't hold device lock while reading the "descriptors" sysfs file") this race couldn't occur, because the routines were mutually exclusive thanks to the device locking. Removing that locking from read_descriptors() exposed it to the race. The best way to fix the bug is to keep hub_port_init() from changing udev->descriptor once udev has been initialized and registered. Drivers expect the descriptors stored in the kernel to be immutable; we should not undermine this expectation. In fact, this change should have been made long ago. So now hub_port_init() will take an additional argument, specifying a buffer in which to store the device descriptor it reads. (If udev has not yet been initialized, the buffer pointer will be NULL and then hub_port_init() will store the device descriptor in udev as before.) This eliminates the data race responsible for the out-of-bounds read. The changes to hub_port_init() appear more extensive than they really are, because of indentation changes resulting from an attempt to avoid writing to other parts of the usb_device structure after it has been initialized. Similar changes should be made to the code that reads the BOS descriptor, but that can be handled in a separate patch later on. This patch is sufficient to fix the bug found by syzbot.
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*

History

21 Nov 2024, 08:40

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/7fe9d87996062f5eb0ca476ad0257f79bf43aaf5 - Mailing List, Patch () https://git.kernel.org/stable/c/7fe9d87996062f5eb0ca476ad0257f79bf43aaf5 - Mailing List, Patch
References () https://git.kernel.org/stable/c/8186596a663506b1124bede9fde6f243ef9f37ee - Mailing List, Patch () https://git.kernel.org/stable/c/8186596a663506b1124bede9fde6f243ef9f37ee - Mailing List, Patch
References () https://git.kernel.org/stable/c/9d241c5d9a9b7ad95c90c6520272fe404d5ac88f - Mailing List, Patch () https://git.kernel.org/stable/c/9d241c5d9a9b7ad95c90c6520272fe404d5ac88f - Mailing List, Patch
References () https://git.kernel.org/stable/c/b4a074b1fb222164ed7d5c0b8c922dc4a0840848 - Mailing List, Patch () https://git.kernel.org/stable/c/b4a074b1fb222164ed7d5c0b8c922dc4a0840848 - Mailing List, Patch
References () https://git.kernel.org/stable/c/b9fbfb349eacc0820f91c797d7f0a3ac7a4935b5 - Mailing List, Patch () https://git.kernel.org/stable/c/b9fbfb349eacc0820f91c797d7f0a3ac7a4935b5 - Mailing List, Patch
References () https://git.kernel.org/stable/c/ff33299ec8bb80cdcc073ad9c506bd79bb2ed20b - Mailing List, Patch () https://git.kernel.org/stable/c/ff33299ec8bb80cdcc073ad9c506bd79bb2ed20b - Mailing List, Patch

21 Aug 2024, 17:28

Type Values Removed Values Added
References () https://git.kernel.org/stable/c/7fe9d87996062f5eb0ca476ad0257f79bf43aaf5 - () https://git.kernel.org/stable/c/7fe9d87996062f5eb0ca476ad0257f79bf43aaf5 - Mailing List, Patch
References () https://git.kernel.org/stable/c/8186596a663506b1124bede9fde6f243ef9f37ee - () https://git.kernel.org/stable/c/8186596a663506b1124bede9fde6f243ef9f37ee - Mailing List, Patch
References () https://git.kernel.org/stable/c/9d241c5d9a9b7ad95c90c6520272fe404d5ac88f - () https://git.kernel.org/stable/c/9d241c5d9a9b7ad95c90c6520272fe404d5ac88f - Mailing List, Patch
References () https://git.kernel.org/stable/c/b4a074b1fb222164ed7d5c0b8c922dc4a0840848 - () https://git.kernel.org/stable/c/b4a074b1fb222164ed7d5c0b8c922dc4a0840848 - Mailing List, Patch
References () https://git.kernel.org/stable/c/b9fbfb349eacc0820f91c797d7f0a3ac7a4935b5 - () https://git.kernel.org/stable/c/b9fbfb349eacc0820f91c797d7f0a3ac7a4935b5 - Mailing List, Patch
References () https://git.kernel.org/stable/c/ff33299ec8bb80cdcc073ad9c506bd79bb2ed20b - () https://git.kernel.org/stable/c/ff33299ec8bb80cdcc073ad9c506bd79bb2ed20b - Mailing List, Patch
First Time Linux linux Kernel
Linux
Summary
  • (es) En el kernel de Linux, se resolvió la siguiente vulnerabilidad: USB: core: corrige la ejecución al no sobrescribir udev-&gt;descriptor en hub_port_init() Syzbot informó una lectura fuera de los límites en sysfs.c:read_descriptors(): ERROR: KASAN : slab-out-of-bounds in read_descriptors+0x263/0x280 drivers/usb/core/sysfs.c:883 Lectura de tamaño 8 en addr ffff88801e78b8c8 por tarea udevd/5011 CPU: 0 PID: 5011 Comm: udevd No contaminado 6.4. 0-rc6-syzkaller-00195-g40f71e7cd3c6 #0 Nombre del hardware: Google Google Compute Engine/Google Compute Engine, BIOS Google 27/05/2023 Seguimiento de llamadas: __dump_stack lib/dump_stack.c:88 [en línea] dump_stack_lvl+0xd9 /0x150 lib/dump_stack.c:106 print_address_description.constprop.0+0x2c/0x3c0 mm/kasan/report.c:351 print_report mm/kasan/report.c:462 [en línea] kasan_report+0x11c/0x130 mm/kasan/report .c:572 read_descriptors+0x263/0x280 drivers/usb/core/sysfs.c:883 ... Asignado por la tarea 758: ... __do_kmalloc_node mm/slab_common.c:966 [en línea] __kmalloc+0x5e/0x190 mm/slab_common .c:979 kmalloc include/linux/slab.h:563 [en línea] kzalloc include/linux/slab.h:680 [en línea] usb_get_configuration+0x1f7/0x5170 drivers/usb/core/config.c:887 usb_enumerate_device drivers/usb /core/hub.c:2407 [en línea] usb_new_device+0x12b0/0x19d0 drivers/usb/core/hub.c:2545 Según lo analizado por Khazhy Kumykov, la causa de este error es una ejecución entre read_descriptors() y hub_port_init(): La primera rutina usa un campo en udev-&gt;descriptor, sin esperar que cambie, mientras que la segunda lo sobrescribe. Antes de commit 45bf39f8df7f ("USB: core: No mantener bloqueado el dispositivo mientras lee el archivo sysfs de "descriptores") esta ejecución no podía ocurrir porque las rutinas eran mutuamente excluyentes gracias al bloqueo del dispositivo. Quitar ese bloqueo de read_descriptors() lo expuso a la ejecución. La mejor manera de corregir el error es evitar que hub_port_init() cambie el descriptor udev-&gt;una vez que udev se haya inicializado y registrado. Los controladores esperan que los descriptores almacenados en el kernel sean inmutables; No debemos socavar esta expectativa. De hecho, este cambio debería haberse realizado hace mucho tiempo. Entonces ahora hub_port_init() tomará un argumento adicional, especificando un búfer en el cual almacenar el descriptor del dispositivo que lee. (Si udev aún no se ha inicializado, el puntero del búfer será NULL y luego hub_port_init() almacenará el descriptor del dispositivo en udev como antes). Esto elimina la ejecución de datos responsable de la lectura fuera de los límites. Los cambios en hub_port_init() parecen más extensos de lo que realmente son, debido a los cambios de sangría resultantes de un intento de evitar escribir en otras partes de la estructura usb_device después de que se haya inicializado. Se deben realizar cambios similares en el código que lee el descriptor BOS, pero eso se puede manejar en un parche separado más adelante. Este parche es suficiente para corregir el error encontrado por syzbot.
CPE cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
CWE CWE-125
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 6.4

16 Jul 2024, 10:15

Type Values Removed Values Added
New CVE

Information

Published : 2024-07-16 10:15

Updated : 2024-11-21 08:40


NVD link : CVE-2023-52886

Mitre link : CVE-2023-52886

CVE.ORG link : CVE-2023-52886


JSON object : View

Products Affected

linux

  • linux_kernel
CWE
CWE-125

Out-of-bounds Read