CVE-2023-52584
spmi: mediatek: Fix UAF on device remove
Description
In the Linux kernel, the following vulnerability has been resolved: spmi: mediatek: Fix UAF on device remove The pmif driver data that contains the clocks is allocated along with spmi_controller. On device remove, spmi_controller will be freed first, and then devres , including the clocks, will be cleanup. This leads to UAF because putting the clocks will access the clocks in the pmif driver data, which is already freed along with spmi_controller. This can be reproduced by enabling DEBUG_TEST_DRIVER_REMOVE and building the kernel with KASAN. Fix the UAF issue by using unmanaged clk_bulk_get() and putting the clocks before freeing spmi_controller.
INFO
Published Date :
March 6, 2024, 7:15 a.m.
Last Modified :
March 14, 2025, 6:58 p.m.
Remotely Exploit :
Yes !
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | LOW | 134c704f-9b21-4f2e-91b3-4a467353bcc0 |
Solution
- Update the Linux kernel package.
- Reboot the system after patching.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2023-52584.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2023-52584 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2023-52584
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2023-52584 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2023-52584 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Mar. 14, 2025
Action Type Old Value New Value Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 from (excluding) 6.7.4 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 from (excluding) 6.6.16 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (excluding) 6.1.77 Added Reference Type CVE: https://git.kernel.org/stable/c/521f28eedd6b14228c46e3b81e3bf9b90c2818d8 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/521f28eedd6b14228c46e3b81e3bf9b90c2818d8 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/9a3881b1f07db1bb55cb0108e6f05cfd027eaf2e Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/9a3881b1f07db1bb55cb0108e6f05cfd027eaf2e Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/e821d50ab5b956ed0effa49faaf29912fd4106d9 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/e821d50ab5b956ed0effa49faaf29912fd4106d9 Types: Patch Added Reference Type CVE: https://git.kernel.org/stable/c/f8dcafcb54632536684336161da8bdd52120f95e Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/f8dcafcb54632536684336161da8bdd52120f95e Types: Patch -
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://git.kernel.org/stable/c/521f28eedd6b14228c46e3b81e3bf9b90c2818d8 Added Reference https://git.kernel.org/stable/c/9a3881b1f07db1bb55cb0108e6f05cfd027eaf2e Added Reference https://git.kernel.org/stable/c/e821d50ab5b956ed0effa49faaf29912fd4106d9 Added Reference https://git.kernel.org/stable/c/f8dcafcb54632536684336161da8bdd52120f95e -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Aug. 06, 2024
Action Type Old Value New Value Added CWE CISA-ADP CWE-416 Added CVSS V3.1 CISA-ADP AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 28, 2024
Action Type Old Value New Value -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
May. 14, 2024
Action Type Old Value New Value -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Mar. 06, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: spmi: mediatek: Fix UAF on device remove The pmif driver data that contains the clocks is allocated along with spmi_controller. On device remove, spmi_controller will be freed first, and then devres , including the clocks, will be cleanup. This leads to UAF because putting the clocks will access the clocks in the pmif driver data, which is already freed along with spmi_controller. This can be reproduced by enabling DEBUG_TEST_DRIVER_REMOVE and building the kernel with KASAN. Fix the UAF issue by using unmanaged clk_bulk_get() and putting the clocks before freeing spmi_controller. Added Reference Linux https://git.kernel.org/stable/c/521f28eedd6b14228c46e3b81e3bf9b90c2818d8 [No types assigned] Added Reference Linux https://git.kernel.org/stable/c/f8dcafcb54632536684336161da8bdd52120f95e [No types assigned] Added Reference Linux https://git.kernel.org/stable/c/9a3881b1f07db1bb55cb0108e6f05cfd027eaf2e [No types assigned] Added Reference Linux https://git.kernel.org/stable/c/e821d50ab5b956ed0effa49faaf29912fd4106d9 [No types assigned]