Skip to main content

CVE-2024-26942: Vulnerability in Linux Linux

Medium
VulnerabilityCVE-2024-26942cvecve-2024-26942
Published: Wed May 01 2024 (05/01/2024, 05:17:56 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: net: phy: qcom: at803x: fix kernel panic with at8031_probe On reworking and splitting the at803x driver, in splitting function of at803x PHYs it was added a NULL dereference bug where priv is referenced before it's actually allocated and then is tried to write to for the is_1000basex and is_fiber variables in the case of at8031, writing on the wrong address. Fix this by correctly setting priv local variable only after at803x_probe is called and actually allocates priv in the phydev struct.

AI-Powered Analysis

AILast updated: 06/29/2025, 13:26:24 UTC

Technical Analysis

CVE-2024-26942 is a medium-severity vulnerability identified in the Linux kernel's network PHY driver for Qualcomm at803x series, specifically affecting the at8031 PHY device. The vulnerability arises from a NULL pointer dereference bug introduced during a rework and splitting of the at803x driver code. In the flawed implementation, the 'priv' pointer, which is intended to reference private driver data, is accessed before it is properly allocated. This premature dereference leads to writes to an invalid memory address when setting the 'is_1000basex' and 'is_fiber' variables for the at8031 device. The consequence of this bug is a kernel panic, causing a denial of service (DoS) condition by crashing the affected system. The fix involves correctly initializing the 'priv' pointer only after the 'at803x_probe' function has allocated the private data structure within the 'phydev' struct, preventing invalid memory access. The CVSS v3.1 base score is 5.5, reflecting a medium severity level, with the vector indicating local attack vector (AV:L), low attack complexity (AC:L), requiring privileges (PR:L), no user interaction (UI:N), unchanged scope (S:U), no impact on confidentiality or integrity (C:N/I:N), but high impact on availability (A:H). No known exploits are currently reported in the wild. The vulnerability is categorized under CWE-362 (Race Condition), which aligns with improper handling of resource initialization leading to unsafe memory access.

Potential Impact

For European organizations, the primary impact of CVE-2024-26942 is the potential for denial of service on Linux systems utilizing the Qualcomm at803x PHY driver, particularly the at8031 variant. Such systems may experience kernel panics leading to unexpected reboots or service interruptions. This can affect network infrastructure devices, embedded systems, or servers running Linux kernels with this driver version. Availability disruptions could impact critical services, especially in sectors relying on stable network connectivity such as telecommunications, finance, healthcare, and industrial control systems. Since the vulnerability requires local privileges and does not affect confidentiality or integrity, the risk of data breach or unauthorized data modification is low. However, the ability of an attacker with local access to cause system crashes could be leveraged in multi-tenant environments or by malicious insiders to degrade service reliability. European organizations with Linux-based network equipment or embedded devices using Qualcomm at803x PHYs should assess their exposure. The absence of known exploits reduces immediate threat but patching is recommended to prevent potential future exploitation.

Mitigation Recommendations

To mitigate CVE-2024-26942, European organizations should: 1) Identify Linux systems running kernels with the affected Qualcomm at803x PHY driver, focusing on versions prior to the patch date (May 2024). 2) Apply the official Linux kernel patches that correct the initialization sequence of the 'priv' pointer in the at803x driver, ensuring the fix is included in kernel updates or backported to long-term support (LTS) kernels where applicable. 3) For embedded or network devices with custom Linux builds, coordinate with vendors or internal development teams to integrate the patch and redeploy updated firmware or kernel images. 4) Restrict local access to systems running vulnerable drivers to trusted personnel only, minimizing the risk of privilege misuse. 5) Monitor system logs for kernel panics or crashes related to PHY driver activity as an indicator of attempted exploitation or instability. 6) Implement robust system recovery and redundancy plans to maintain availability in case of unexpected crashes. 7) Consider deploying kernel hardening features and runtime protections that can mitigate the impact of memory corruption bugs. These steps go beyond generic advice by emphasizing vendor coordination for embedded systems, local access control, and proactive monitoring specific to this PHY driver vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-02-19T14:20:24.197Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682d9829c4522896dcbe2ed0

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

Last enriched: 6/29/2025, 1:26:24 PM

Last updated: 8/16/2025, 3:04:12 PM

Views: 14

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