Skip to main content

CVE-2024-50058: Vulnerability in Linux Linux

High
VulnerabilityCVE-2024-50058cvecve-2024-50058
Published: Mon Oct 21 2024 (10/21/2024, 19:39:48 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

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.

AI-Powered Analysis

AILast updated: 06/28/2025, 16:41:51 UTC

Technical Analysis

CVE-2024-50058 is a vulnerability identified in the Linux kernel's serial subsystem, specifically related to the handling of UART (Universal Asynchronous Receiver/Transmitter) port shutdown operations. The issue arises from an inconsistent null-pointer check in the uart_shutdown() function. A recent commit (af224ca2df29) introduced some null-pointer checks for the uart_port structure (uport), assuming that uport could be NULL in uart_shutdown(). However, immediately after this check, there is an unprotected dereference of uport in the call to uart_port_dtr_rts(uport, false), which is executed if the HUPCL (hang up on close) flag is set. This inconsistency could lead to a null-pointer dereference if uport is indeed NULL at this point, potentially causing a kernel panic or system crash. The vulnerability was discovered through static analysis (Coverity CID 1585130) and has been acknowledged by the Linux kernel maintainers. Although the exact conditions under which uport can be NULL here are not fully confirmed, the presence of this unsafe dereference represents a stability and security risk. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet. The vulnerability affects specific Linux kernel versions identified by the commit hash 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, indicating it is a recent regression or flaw in the kernel's serial driver code.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to systems running affected Linux kernel versions, especially those utilizing serial communication interfaces. Industrial control systems, embedded devices, telecommunications infrastructure, and servers that rely on UART ports for management or communication could experience unexpected kernel crashes or denial of service conditions if this vulnerability is triggered. Such disruptions could lead to operational downtime, loss of availability, and potential cascading effects in critical infrastructure environments. While the vulnerability does not directly imply privilege escalation or data leakage, the resulting system instability could be exploited by attackers to cause denial of service or to facilitate further attacks by forcing reboots or interrupting security monitoring. Organizations with Linux-based IoT devices or network equipment using serial ports are particularly at risk. Given the widespread use of Linux in European data centers, cloud environments, and embedded systems, the impact could be significant if unpatched systems are exposed to conditions that trigger this flaw.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should: 1) Identify and inventory all Linux systems running the affected kernel versions, focusing on those using serial ports or UART interfaces. 2) Apply the latest Linux kernel patches or updates that address CVE-2024-50058 as soon as they become available from trusted sources or vendor distributions. 3) Temporarily disable or restrict access to serial ports where feasible, especially on critical systems, to reduce the attack surface until patches are applied. 4) Implement monitoring for kernel crashes or unusual system reboots that could indicate exploitation attempts. 5) For embedded or IoT devices, coordinate with device manufacturers to obtain firmware updates incorporating the fix. 6) Conduct thorough testing of kernel updates in staging environments to ensure stability before deployment in production. 7) Employ strict access controls and network segmentation to limit exposure of vulnerable systems to untrusted users or networks. These steps go beyond generic advice by emphasizing inventory, access restriction, and proactive monitoring tailored to the nature of the vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-10-21T19:36:19.938Z
Cisa Enriched
true
Cvss Version
null
State
PUBLISHED

Threat ID: 682d9824c4522896dcbdfe0e

Added to database: 5/21/2025, 9:08:52 AM

Last enriched: 6/28/2025, 4:41:51 PM

Last updated: 8/3/2025, 6:48:21 AM

Views: 11

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats