CVE-2024-50058
"Linux kernel Derefence in UART shutdown"
Description
In the Linux kernel, the following vulnerability has been resolved: serial: protect uart_port_dtr_rts() in uart_shutdown() too Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected "uart_port_dtr_rts(uport, false);" call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports. Or it cannot be NULL at this point at all for some reason :P. Until the above is investigated, stay on the safe side and move this dereference to the if too. I got this inconsistency from Coverity under CID 1585130. Thanks.
INFO
Published Date :
Oct. 21, 2024, 8:15 p.m.
Last Modified :
Nov. 8, 2024, 4:15 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-50058
.
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-50058
vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-50058
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.
-
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Nov. 08, 2024
Action Type Old Value New Value Added Reference kernel.org https://git.kernel.org/stable/c/2fe399bb8efd0d325ab1138cf8e3ecf23a39e96d [No types assigned] -
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Nov. 04, 2024
Action Type Old Value New Value Added Reference kernel.org https://git.kernel.org/stable/c/399927f0f875b93f3d5a0336d382ba48b8671eb2 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/d7b5876a6e74cdf8468a478be6b23f2f5464ac7a [No types assigned] -
Initial Analysis by [email protected]
Oct. 24, 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/602babaa84d627923713acaf5f7e9a4369e77473 No Types Assigned https://git.kernel.org/stable/c/602babaa84d627923713acaf5f7e9a4369e77473 Patch Changed Reference Type https://git.kernel.org/stable/c/76ed24a34223bb2c6b6162e1d8389ec4e602a290 No Types Assigned https://git.kernel.org/stable/c/76ed24a34223bb2c6b6162e1d8389ec4e602a290 Patch Changed Reference Type https://git.kernel.org/stable/c/e418d91195d29d5f9c9685ff309b92b04b41dc40 No Types Assigned https://git.kernel.org/stable/c/e418d91195d29d5f9c9685ff309b92b04b41dc40 Patch Added CWE NIST CWE-476 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions up to (excluding) 6.6.57 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.11.4 -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Oct. 21, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: serial: protect uart_port_dtr_rts() in uart_shutdown() too Commit af224ca2df29 (serial: core: Prevent unsafe uart port access, part 3) added few uport == NULL checks. It added one to uart_shutdown(), so the commit assumes, uport can be NULL in there. But right after that protection, there is an unprotected "uart_port_dtr_rts(uport, false);" call. That is invoked only if HUPCL is set, so I assume that is the reason why we do not see lots of these reports. Or it cannot be NULL at this point at all for some reason :P. Until the above is investigated, stay on the safe side and move this dereference to the if too. I got this inconsistency from Coverity under CID 1585130. Thanks. Added Reference kernel.org https://git.kernel.org/stable/c/e418d91195d29d5f9c9685ff309b92b04b41dc40 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/76ed24a34223bb2c6b6162e1d8389ec4e602a290 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/602babaa84d627923713acaf5f7e9a4369e77473 [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-50058
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-50058
weaknesses.