CVE-2023-54026
Description
In the Linux kernel, the following vulnerability has been resolved:
opp: Fix use-after-free in lazy_opp_tables after probe deferral
When dev_pm_opp_of_find_icc_paths() in _allocate_opp_table() returns -EPROBE_DEFER, the opp_table is freed again, to wait until all the interconnect paths are available.
However, if the OPP table is using required-opps then it may already have been added to the global lazy_opp_tables list. The error path does not remove the opp_table from the list again.
This can cause crashes later when the provider of the required-opps is added, since we will iterate over OPP tables that have already been freed. E.g.:
Unable to handle kernel NULL pointer dereference when read CPU: 0 PID: 7 Comm: kworker/0:0 Not tainted 6.4.0-rc3 PC is at _of_add_opp_table_v2 (include/linux/of.h:949 drivers/opp/of.c:98 drivers/opp/of.c:344 drivers/opp/of.c:404 drivers/opp/of.c:1032) -> lazy_link_required_opp_table()
Fix this by calling _of_clear_opp_table() to remove the opp_table from the list and clear other allocated resources. While at it, also add the missing mutex_destroy() calls in the error path.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Use-after-free in Linux kernel OPP subsystem due to missing list removal during probe deferral, causing potential crash.
A use-after-free vulnerability exists in the Linux kernel's Operating Performance Points (OPP) framework. When dev_pm_opp_of_find_icc_paths() returns -EPROBE_DEFER during _allocate_opp_table(), the opp_table is freed to wait for interconnect paths. However, if the OPP table uses required-opps, it may already be added to the global lazy_opp_tables list. The error path does not remove the table from this list, leading to a dangling pointer.
An attacker can trigger this condition by causing a device probe to defer and then having the required-opp provider added later. The vulnerability is triggered when the system iterates over the lazy_opp_tables list to link required-opps, resulting in a use-after-free. The crash manifests as a NULL pointer dereference in _of_add_opp_table_v2() (specifically lazy_link_required_opp_table()) as shown in the kernel panic.
The impact includes denial of service via kernel crash and potentially arbitrary code execution if an attacker can control the freed memory. The vulnerability is local and requires control over device probe ordering.
The fix, included in Linux kernel stable commit c05e76d6b249, calls _of_clear_opp_table() to remove the table from the list and adds missing mutex_destroy() calls [1]. Users should apply the latest kernel updates to mitigate this issue.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
439a0e723d35076ab057de777c05e76d6b249b2a2ab039bd5Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
4News mentions
0No linked articles in our index yet.