CVE-2023-52584
LowIn 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.
CVSS 3.1 score
3.8
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N
Weakness type
CWE-416CVE-2023-52584 is a Use After Free vulnerability
What is Use After Free?
The product references memory after it has been freed, which may cause it to crash, use unexpected values, or execute code. Learn more on MITRE CWE
Affected versions
Linux kernel versions
5.17
and later are affected. Fixed in
6.1.77,
6.6.16,
6.7.4,
6.8
and their respective stable series.
References
4 total-
Patch
-
Patch
-
Patch
-
Patch
Frequently asked questions
-
What is CVE-2023-52584?
CVE-2023-52584 is a Low severity Linux kernel vulnerability with a CVSS score of 3.8 out of 10 , classified as an Use After Free flaw (CWE-416) . It affects Linux kernel versions from 5.17 onward and has been patched in 6.1.77, 6.6.16, 6.7.4 and others. CVE-2023-52584 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2023-52584?
CVE-2023-52584 has a CVSS score of 3.8 out of 10, rated Low severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N. -
Is there a patch available for CVE-2023-52584?
Yes. CVE-2023-52584 has been patched. Fixed versions include 6.1.77, 6.6.16, 6.7.4 and others. If you are running Linux kernel 5.17 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2023-52584 actively exploited?
No. CVE-2023-52584 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.