In the Linux kernel, the following vulnerability has been resolved:
HID: usbhid: fix info leak in hid_submit_ctrl
In hid_submit_ctrl(), the way of calculating the report length doesnt take into account that report->size can be zero. When running the syzkaller reproducer, a report of size 0 causes hid_submit_ctrl) to calculate transfer_buffer_length as 16384. When this urb is passed to the usb core layer, KMSAN reports an info leak of 16384 bytes.
To fix this, first modify hid_report_len() to account for the zero report size case by using DIV_ROUND_UP for the division. Then, call it from hid_submit_ctrl().
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Linux_kernel | Linux | * | 4.4.274 (excluding) |
| Linux_kernel | Linux | 4.5.0 (including) | 4.9.274 (excluding) |
| Linux_kernel | Linux | 4.10.0 (including) | 4.14.238 (excluding) |
| Linux_kernel | Linux | 4.15.0 (including) | 4.19.196 (excluding) |
| Linux_kernel | Linux | 4.20.0 (including) | 5.4.127 (excluding) |
| Linux_kernel | Linux | 5.5.0 (including) | 5.10.45 (excluding) |
| Linux_kernel | Linux | 5.11.0 (including) | 5.12.12 (excluding) |
Resources such as files and directories may be inadvertently exposed through mechanisms such as insecure permissions, or when a program accidentally operates on the wrong object. For example, a program may intend that private files can only be provided to a specific user. This effectively defines a control sphere that is intended to prevent attackers from accessing these private files. If the file permissions are insecure, then parties other than the user will be able to access those files. A separate control sphere might effectively require that the user can only access the private files, but not any other files on the system. If the program does not ensure that the user is only requesting private files, then the user might be able to access other files on the system. In either case, the end result is that a resource has been exposed to the wrong party.