Answer in brief
CVE-2023-54026 records a High severity (CVSS 7.8) vulnerability in opp: Fix use-after-free in lazy_opp_tables after probe deferral. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7eba0c7641b0009818e469dbfcdd87a0155ab9d4 <39a0e723d3502f6dc4c603f57ebe8dc7bcc4a4bc || >=7eba0c7641b0009818e469dbfcdd87a0155ab9d4 <76ab057de777723ec924654502d1a260ba7d7d54 || >=7eba0c7641b0009818e469dbfcdd87a0155ab9d4 <c05e76d6b249e5254c31994eedd06dd3cc90dee0 || >=7eba0c7641b0009818e469dbfcdd87a0155ab9d4 <b2a2ab039bd58f51355e33d7d3fc64605d7f870d | 39a0e723d3502f6dc4c603f57ebe8dc7bcc4a4bc, 76ab057de777723ec924654502d1a260ba7d7d54, c05e76d6b249e5254c31994eedd06dd3cc90dee0, b2a2ab039bd58f51355e33d7d3fc64605d7f870d |
| Linux/Linuxgeneric | 5.12 | Not reported |
Published upstream
Dec 24, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2023-54026 records a High severity (CVSS 7.8) vulnerability in opp: Fix use-after-free in lazy_opp_tables after probe deferral. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=7eba0c7641b0009818e469dbfcdd87a0155ab9d4 <39a0e723d3502f6dc4c603f57ebe8dc7bcc4a4bc || >=7eba0c7641b0009818e469dbfcdd87a0155ab9d4 <76ab057de777723ec924654502d1a260ba7d7d54 || >=7eba0c7641b0009818e469dbfcdd87a0155ab9d4 <c05e76d6b249e5254c31994eedd06dd3cc90dee0 || >=7eba0c7641b0009818e469dbfcdd87a0155ab9d4 <b2a2ab039bd58f51355e33d7d3fc64605d7f870d | 39a0e723d3502f6dc4c603f57ebe8dc7bcc4a4bc, 76ab057de777723ec924654502d1a260ba7d7d54, c05e76d6b249e5254c31994eedd06dd3cc90dee0, b2a2ab039bd58f51355e33d7d3fc64605d7f870d |
| Linux/Linuxgeneric | 5.12 | Not reported |
Published upstream
Dec 24, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
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.
Quoted source text, attributed separately from HOL analysis.