CVE-2024-46675
Samsung Exynos USB Core Event Buffer Access Vulnerability
Description
In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: core: Prevent USB core invalid event buffer address access This commit addresses an issue where the USB core could access an invalid event buffer address during runtime suspend, potentially causing SMMU faults and other memory issues in Exynos platforms. The problem arises from the following sequence. 1. In dwc3_gadget_suspend, there is a chance of a timeout when moving the USB core to the halt state after clearing the run/stop bit by software. 2. In dwc3_core_exit, the event buffer is cleared regardless of the USB core's status, which may lead to an SMMU faults and other memory issues. if the USB core tries to access the event buffer address. To prevent this hardware quirk on Exynos platforms, this commit ensures that the event buffer address is not cleared by software when the USB core is active during runtime suspend by checking its status before clearing the buffer address.
INFO
Published Date :
Sept. 13, 2024, 6:15 a.m.
Last Modified :
Sept. 20, 2024, 5:18 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
1.8
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-2024-46675.
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-2024-46675 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-46675 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]
Sep. 20, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H Changed Reference Type https://git.kernel.org/stable/c/111277b881def3153335acfe0d1f43e6cd83ac93 No Types Assigned https://git.kernel.org/stable/c/111277b881def3153335acfe0d1f43e6cd83ac93 Patch Changed Reference Type https://git.kernel.org/stable/c/14e497183df28c006603cc67fd3797a537eef7b9 No Types Assigned https://git.kernel.org/stable/c/14e497183df28c006603cc67fd3797a537eef7b9 Patch Changed Reference Type https://git.kernel.org/stable/c/2189fd13c577d7881f94affc09c950a795064c4b No Types Assigned https://git.kernel.org/stable/c/2189fd13c577d7881f94affc09c950a795064c4b Patch Changed Reference Type https://git.kernel.org/stable/c/7bb11a75dd4d3612378b90e2a4aa49bdccea28ab No Types Assigned https://git.kernel.org/stable/c/7bb11a75dd4d3612378b90e2a4aa49bdccea28ab Patch Changed Reference Type https://git.kernel.org/stable/c/b72da4d89b97da71e056cc4d1429b2bc426a9c2f No Types Assigned https://git.kernel.org/stable/c/b72da4d89b97da71e056cc4d1429b2bc426a9c2f Patch Changed Reference Type https://git.kernel.org/stable/c/d2afc2bffec77316b90d530b07695e3f534df914 No Types Assigned https://git.kernel.org/stable/c/d2afc2bffec77316b90d530b07695e3f534df914 Patch Changed Reference Type https://git.kernel.org/stable/c/e23f6ad8d110bf632f7471482e10b43dc174fb72 No Types Assigned https://git.kernel.org/stable/c/e23f6ad8d110bf632f7471482e10b43dc174fb72 Patch Changed Reference Type https://git.kernel.org/stable/c/eca3f543f817da87c00d1a5697b473efb548204f No Types Assigned https://git.kernel.org/stable/c/eca3f543f817da87c00d1a5697b473efb548204f Patch Added CWE NIST NVD-CWE-noinfo Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions up to (excluding) 4.19.321 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.20 up to (excluding) 5.4.283 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.5 up to (excluding) 5.10.225 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.166 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.108 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.49 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.10.8 *cpe:2.3:o:linux:linux_kernel:6.11:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.11:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.11:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.11:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.11:rc5:*:*:*:*:*:* -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Sep. 13, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: core: Prevent USB core invalid event buffer address access This commit addresses an issue where the USB core could access an invalid event buffer address during runtime suspend, potentially causing SMMU faults and other memory issues in Exynos platforms. The problem arises from the following sequence. 1. In dwc3_gadget_suspend, there is a chance of a timeout when moving the USB core to the halt state after clearing the run/stop bit by software. 2. In dwc3_core_exit, the event buffer is cleared regardless of the USB core's status, which may lead to an SMMU faults and other memory issues. if the USB core tries to access the event buffer address. To prevent this hardware quirk on Exynos platforms, this commit ensures that the event buffer address is not cleared by software when the USB core is active during runtime suspend by checking its status before clearing the buffer address. Added Reference kernel.org https://git.kernel.org/stable/c/eca3f543f817da87c00d1a5697b473efb548204f [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/d2afc2bffec77316b90d530b07695e3f534df914 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/b72da4d89b97da71e056cc4d1429b2bc426a9c2f [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/111277b881def3153335acfe0d1f43e6cd83ac93 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/2189fd13c577d7881f94affc09c950a795064c4b [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/7bb11a75dd4d3612378b90e2a4aa49bdccea28ab [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/e23f6ad8d110bf632f7471482e10b43dc174fb72 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/14e497183df28c006603cc67fd3797a537eef7b9 [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-46675 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-2024-46675
weaknesses.