phy: qcom: qmp-usb-legacy: fix NULL-deref on runtime suspend
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.6.606.11.76.12In the Linux kernel, the following vulnerability has been resolved:
phy: qcom: qmp-usb-legacy: fix NULL-deref on runtime suspend
Commit 413db06c05e7 ("phy: qcom-qmp-usb: clean up probe initialisation") removed most users of the platform device driver data from the qcom-qmp-usb driver, but mistakenly also removed the initialisation despite the data still being used in the runtime PM callbacks. This bug was later reproduced when the driver was copied to create the qmp-usb-legacy driver.
Restore the driver data initialisation at probe to avoid a NULL-pointer dereference on runtime suspend.
Apparently no one uses runtime PM, which currently needs to be enabled manually through sysfs, with these drivers.
From the CVE record · Linux
The Linux kernel's qmp-usb-legacy driver can dereference a NULL pointer during runtime suspend because driver data is not initialized at probe. This requires runtime power management to be enabled manually through sysfs; the input does not establish whether an attacker can trigger it or what access they would need.
Engineers running Linux kernels with the qmp-usb-legacy driver should check their kernel version; affected versions are not specified.