CVE-2023-54026
Last modified
CVE-2023-54026 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 7eba0c7641b0009818e469dbfcdd87a0155ab9d4, < 39a0e723d3502f6dc4c603f57ebe8dc7bcc4a4bc; >= 7eba0c7641b0009818e469dbfcdd87a0155ab9d4, < 76ab057de777723ec924654502d1a260ba7d7d54; >= 7eba0c7641b0009818e469dbfcdd87a0155ab9d4, < c05e76d6b249e5254c31994eedd06dd3cc90dee0; >= 7eba0c7641b0009818e469dbfcdd87a0155ab9d4, < b2a2ab039bd58f51355e33d7d3fc64605d7f870d |
| Linux | Linux | 5.12 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2023-54026?
How severe is CVE-2023-54026?
How do I fix CVE-2023-54026?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-54020In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54021In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54022In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54023In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54024In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54025In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54027In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54028In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54029Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2023-5403Server hostname translation to IP address manipulation which…8.1
- CVE-2023-54030In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54031In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2023-54026?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
