IT

Tracker / CVE-2024-41035

CVE-2024-41035

Medium 5.5

In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix duplicate endpoint bug by clearing reserved bits in the descriptor Syzbot has identified a bug in usbcore (see the Closes: tag below) caused by our assumption that the reserved bits in an endpoint descriptor's bEndpointAddress field will always be 0. As a result of the bug, the endpoint_is_duplicate() routine in config.c (and possibly other routines as well) may believe that two descriptors are for distinct endpoints, even though they have the same direction and endpoint number. This can lead to confusion, including the bug identified by syzbot (two descriptors with matching endpoint numbers and directions, where one was interrupt and the other was bulk). To fix the bug, we will clear the reserved bits in bEndpointAddress when we parse the descriptor. (Note that both the USB-2.0 and USB-3.1 specs say these bits are "Reserved, reset to zero".) This requires us to make a copy of the descriptor earlier in usb_parse_endpoint() and use the copy instead of the original when checking for duplicates.

Affected products and versions

linux linux_kernel
linux linux_kernel · 3.10.106 → 3.11
linux linux_kernel · 3.12.70 → 3.13
linux linux_kernel · 3.16.42 → 3.17
linux linux_kernel · 3.2.87 → 3.3
linux linux_kernel · 4.1.39 → 4.2
linux linux_kernel · 4.10.1 → 4.19.318
linux linux_kernel · 4.20 → 5.4.280
linux linux_kernel · 4.4.42 → 4.5
linux linux_kernel · 4.9.3 → 4.10
linux linux_kernel · 5.11 → 5.15.163
linux linux_kernel · 5.16 → 6.1.100
linux linux_kernel · 5.5 → 5.10.222
linux linux_kernel · 6.2 → 6.6.41
linux linux_kernel · 6.7 → 6.9.10

Analysis

This page is not indexable yet.Until it carries original analysis — what it actually exposes, how to check in two minutes whether a system was touched, what to do if it was — the page stays noindex. The database decides that, not the template.

References