usb: acpi: Prevent null pointer dereference in usb_acpi_add_usb4_devlink()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.12.346.15.36.16In the Linux kernel, the following vulnerability has been resolved:
usb: acpi: Prevent null pointer dereference in usb_acpi_add_usb4_devlink()
As demonstrated by the fix for update_port_device_state, commit 12783c0b9e2c ("usb: core: Prevent null pointer dereference in update_port_device_state"), usb_hub_to_struct_hub() can return NULL in certain scenarios, such as during hub driver unbind or teardown race conditions, even if the underlying usb_device structure exists.
Plus, all other places that call usb_hub_to_struct_hub() in the same file do check for NULL return values.
If usb_hub_to_struct_hub() returns NULL, the subsequent access to hub->ports[udev->portnum - 1] will cause a null pointer dereference.
From the CVE record · Linux
The Linux kernel’s USB ACPI function usb_acpi_add_usb4_devlink() can dereference a null pointer if a hub lookup returns NULL during hub driver unbind or teardown. The input does not specify an attacker action, access requirement, or user interaction needed to trigger the condition.
Engineers running the Linux kernel should check their systems; affected versions are not specified.