CVE-2024-41035

USB: core: Fix duplicate endpoint bug by clearing reserved bits in the descriptor

State
Published
Severity
Not scored
Published
Jul 29, 2024
Updated
May 23, 2026
Reserved
Jul 12, 2024

Read the record on cve.org

Description

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 0a8fd1346254974c3a852338508e4a4cddbb35f1 to before d8418fd083d1b90a6c007cf8dcf81aeae274727bAffected
  • 0a8fd1346254974c3a852338508e4a4cddbb35f1 to before 60abea505b726b38232a0ef410d2bd1994a77f78Affected
  • 0a8fd1346254974c3a852338508e4a4cddbb35f1 to before d09dd21bb5215d583ca9a1cb1464dbc77a7e88cfAffected
  • 0a8fd1346254974c3a852338508e4a4cddbb35f1 to before 2bd8534a1b83c65702aec3cab164170f8e584188Affected
  • 0a8fd1346254974c3a852338508e4a4cddbb35f1 to before 9edcf317620d7c6a8354911b69b874cf89716646Affected
  • 0a8fd1346254974c3a852338508e4a4cddbb35f1 to before 647d61aef106dbed9c70447bcddbd4968e67ca64Affected
  • 0a8fd1346254974c3a852338508e4a4cddbb35f1 to before 37514a5c1251a8c5c95c323f55050736e7069ac7Affected
  • 0a8fd1346254974c3a852338508e4a4cddbb35f1 to before a368ecde8a5055b627749b09c6218ef793043e47Affected
  • c3726b442527ab31c7110d0445411f5b5343db01Affected
  • 15668b4354b38b41b316571deed2763d631b2977Affected
  • 8597a9245181656ae2ef341906e5f40af323fbcaAffected
  • 264024a2676ba7d91fe7b1713b2c32d1b0b508cbAffected
  • b0de742a1be16b76b534d088682f18cf57f012d2Affected
  • 7cc00abef071a8a7d0f4457b7afa2f57f683d83fAffected
  • 05b0f2fc3c2f9efda47439557e0d51faca7e43edAffected
  • 3.2.87 to before 3.3Affected
  • 3.10.106 to before 3.11Affected
  • 3.12.70 to before 3.13Affected
  • 3.16.42 to before 3.17Affected
  • 4.1.39 to before 4.2Affected
  • 4.4.42 to before 4.5Affected
  • 4.9.3 to before 4.10Affected
LinuxLinux
  • 4.10Affected
  • before 4.10Not affected
  • 4.19.318 through 4.19.*Not affected
  • 5.4.280 through 5.4.*Not affected
  • 5.10.222 through 5.10.*Not affected
  • 5.15.163 through 5.15.*Not affected
  • 6.1.100 through 6.1.*Not affected
  • 6.6.41 through 6.6.*Not affected
  • 6.9.10 through 6.9.*Not affected
  • 6.10 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.