CVE-2024-38633
Linux Kernel MAX3100 UART Driver Null Pointer Dereference Vulnerability
Description
In the Linux kernel, the following vulnerability has been resolved: serial: max3100: Update uart_driver_registered on driver removal The removal of the last MAX3100 device triggers the removal of the driver. However, code doesn't update the respective global variable and after insmod — rmmod — insmod cycle the kernel oopses: max3100 spi-PRP0001:01: max3100_probe: adding port 0 BUG: kernel NULL pointer dereference, address: 0000000000000408 ... RIP: 0010:serial_core_register_port+0xa0/0x840 ... max3100_probe+0x1b6/0x280 [max3100] spi_probe+0x8d/0xb0 Update the actual state so next time UART driver will be registered again. Hugo also noticed, that the error path in the probe also affected by having the variable set, and not cleared. Instead of clearing it move the assignment after the successfull uart_register_driver() call.
INFO
Published Date :
June 21, 2024, 11:15 a.m.
Last Modified :
Sept. 9, 2024, 1:53 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-38633.
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-38633 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-38633 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. 09, 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/21a61a7fbcfdd3493cede43ebc7c4dfae2147a8b No Types Assigned https://git.kernel.org/stable/c/21a61a7fbcfdd3493cede43ebc7c4dfae2147a8b Patch Changed Reference Type https://git.kernel.org/stable/c/361a92c9038e8c8c3996f8eeaa14522a8ad90752 No Types Assigned https://git.kernel.org/stable/c/361a92c9038e8c8c3996f8eeaa14522a8ad90752 Patch Changed Reference Type https://git.kernel.org/stable/c/712a1fcb38dc7cac6da63ee79a88708fbf9c45ec No Types Assigned https://git.kernel.org/stable/c/712a1fcb38dc7cac6da63ee79a88708fbf9c45ec Patch Changed Reference Type https://git.kernel.org/stable/c/9db4222ed8cd3e50b81c8b910ae74c26427a4003 No Types Assigned https://git.kernel.org/stable/c/9db4222ed8cd3e50b81c8b910ae74c26427a4003 Patch Changed Reference Type https://git.kernel.org/stable/c/b6eb7aff23e05f362e8c9b560f6ac5e727b70e00 No Types Assigned https://git.kernel.org/stable/c/b6eb7aff23e05f362e8c9b560f6ac5e727b70e00 Patch Changed Reference Type https://git.kernel.org/stable/c/e8a10089eddba40d4b2080c9d3fc2d2b2488f762 No Types Assigned https://git.kernel.org/stable/c/e8a10089eddba40d4b2080c9d3fc2d2b2488f762 Patch Changed Reference Type https://git.kernel.org/stable/c/e8e2a4339decad7e59425b594a98613402652d72 No Types Assigned https://git.kernel.org/stable/c/e8e2a4339decad7e59425b594a98613402652d72 Patch Changed Reference Type https://git.kernel.org/stable/c/fa84ca78b048dfb00df0ef446f5c35e0a98ca6a0 No Types Assigned https://git.kernel.org/stable/c/fa84ca78b048dfb00df0ef446f5c35e0a98ca6a0 Patch Added CWE NIST CWE-476 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 2.6.30 up to (excluding) 4.19.316 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 4.20 up to (excluding) 5.4.278 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.5 up to (excluding) 5.10.219 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.161 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.93 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.33 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.9.4 -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 15, 2024
Action Type Old Value New Value Removed Reference kernel.org https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 27, 2024
Action Type Old Value New Value Added Reference kernel.org https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html [No types assigned] -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 21, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: serial: max3100: Update uart_driver_registered on driver removal The removal of the last MAX3100 device triggers the removal of the driver. However, code doesn't update the respective global variable and after insmod — rmmod — insmod cycle the kernel oopses: max3100 spi-PRP0001:01: max3100_probe: adding port 0 BUG: kernel NULL pointer dereference, address: 0000000000000408 ... RIP: 0010:serial_core_register_port+0xa0/0x840 ... max3100_probe+0x1b6/0x280 [max3100] spi_probe+0x8d/0xb0 Update the actual state so next time UART driver will be registered again. Hugo also noticed, that the error path in the probe also affected by having the variable set, and not cleared. Instead of clearing it move the assignment after the successfull uart_register_driver() call. Added Reference kernel.org https://git.kernel.org/stable/c/21a61a7fbcfdd3493cede43ebc7c4dfae2147a8b [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/9db4222ed8cd3e50b81c8b910ae74c26427a4003 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/e8e2a4339decad7e59425b594a98613402652d72 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/361a92c9038e8c8c3996f8eeaa14522a8ad90752 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/b6eb7aff23e05f362e8c9b560f6ac5e727b70e00 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/e8a10089eddba40d4b2080c9d3fc2d2b2488f762 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/fa84ca78b048dfb00df0ef446f5c35e0a98ca6a0 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/712a1fcb38dc7cac6da63ee79a88708fbf9c45ec [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-38633 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-38633
weaknesses.