Live › vulnerability › CVE-2026-98527
Go to dashboardThe Zynq GPIO driver in the Linux kernel leaks a runtime power-management reference when a GPIO request fails, because the error path does not drop the usage counter. As a result the controller cannot runtime-suspend and its clock stays enabled.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
gpio: zynq: fix runtime PM leak on request error path
pm_runtime_get_sync() leaves the usage counter incremented even when it fails, and zynq_gpio_request() returns the error without dropping it.
gpiolib does not call ->free() when ->request() fails, so zynq_gpio_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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98527")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.