net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ d40261236e8e278cb1936cb5e934262971692b10 · < 02df3170c04a8356cd571ab9155a42f030190abc| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path
syzbot reported that act_len in kalmia_send_init_packet() is uninitialized when passing it to the first usb_bulk_msg error path. Jiri Pirko noted that it's pointless to pass it in the error path, and that the value that would be printed in the second error path would be the value of act_len from the first call to usb_bulk_msg.[1]
With this in mind, let's just not pass act_len to the usb_bulk_msg error paths.
1: https://lore.kernel.org/lkml/Y9pY61y1nwTuzMOa@nanopsycho/
From the CVE record · Linux
In the Linux kernel’s kalmia USB network driver, an error path in kalmia_send_init_packet() can use an uninitialized act_len value. The input does not establish an attacker-controlled impact or specify whether exploitation requires network access, local access, authentication, or user interaction.
Engineers running Linux kernels with the kalmia USB network driver should check their deployments; affected versions are not specified.