Linux kernel runtime PM reference leak in Xilinx GPIO requests
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 26b04774621ed333e8bc56479feb6e31625df58c · < 2fd6ecda5d1f47cffcfadddb35ee49402162c724| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
gpio: xilinx: fix runtime PM leak on request error path
pm_runtime_get_sync() leaves the usage counter incremented even when it fails, and xgpio_request() returns the error without dropping it.
gpiolib does not call ->free() when ->request() fails, so xgpio_free(), which holds the only matching pm_runtime_put(), never runs. The reference is leaked and the controller can no longer runtime-suspend, so its clock stays enabled.
Switch to pm_runtime_resume_and_get(), which only increments the usage counter on success.
From the CVE record · Linux
In the Linux kernel’s Xilinx GPIO driver, a failed GPIO request can leak a runtime power-management reference, preventing the controller from suspending and leaving its clock enabled. The input does not describe an attacker path or specify network access, authentication, or user-interaction requirements.
Engineers running Linux kernels with the Xilinx GPIO driver should check their kernel version; affected versions are not specified.