usb: gadget: f_mass_storage: fix null pointer dereference in fsg_common_set_num_buffers()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ fe5a6c48fd954489f51aab151d5dad9254c76419 · < 9e8dd2a7a8ccbb756771ad985b0ad3387ed3c957| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
usb: gadget: f_mass_storage: fix null pointer dereference in fsg_common_set_num_buffers()
Previously fsg_num_buffers_validate() was removed as it was not necessary due to Kconfig setting the limits for n from 2 to 256 with default as 2. However, setting the page content in such a way that kstrtou8() reflects n value as either 0 or 1 bypasses these restrictions leading to a null pointer dereference if n is 0. Fix this by adding a check for n < 2 and returning -EINVAL if n is either 0 or 1 consistent with Kconfig logic.
From the CVE record · Linux
The Linux kernel USB mass storage gadget can dereference a null pointer when fsg_common_set_num_buffers() receives a buffer count of 0. This can occur if page content is set so that kstrtou8() produces 0, bypassing the Kconfig limits. The input does not specify the access or authentication needed to set that content.
Engineers running Linux kernels with the USB mass storage gadget should check whether their kernel is affected; affected versions are not specified.