net: usb: aqc111: Do not perform PM inside suspend callback
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ e58ba4544c7771591d1e3157bc01b4a8e4d1c3fc · < d3e32a612c6391ca9b7c183aeec22b4fd24c300c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
net: usb: aqc111: Do not perform PM inside suspend callback
syzbot reports "task hung in rpm_resume"
This is caused by aqc111_suspend calling the PM variant of its write_cmd routine.
The simplified call trace looks like this:
rpm_suspend() usb_suspend_both() - here udev->dev.power.runtime_status == RPM_SUSPENDING aqc111_suspend() - called for the usb device interface aqc111_write32_cmd() usb_autopm_get_interface() pm_runtime_resume_and_get() rpm_resume() - here we call rpm_resume() on our parent rpm_resume() - Here we wait for a status change that will never happen.
At this point we block another task which holds rtnl_lock and locks up the whole networking stack.
Fix this by replacing the write_cmd calls with their _nopm variants
From the CVE record · Linux
The Linux kernel’s aqc111 USB network driver can hang during suspend because its callback invokes a power-management operation that waits for a status change that cannot occur. This can block another task holding rtnl_lock and lock up the networking stack. The input does not establish an attacker path or specify network access, authentication, or user-interaction requirements.
Engineers running Linux kernels with the aqc111 USB network driver should check their exposure; affected versions are not specified.