Skip to main content

CVE-2022-49848: Vulnerability in Linux Linux

Medium
VulnerabilityCVE-2022-49848cvecve-2022-49848
Published: Thu May 01 2025 (05/01/2025, 14:10:03 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: phy: qcom-qmp-combo: fix NULL-deref on runtime resume Commit fc64623637da ("phy: qcom-qmp-combo,usb: add support for separate PCS_USB region") started treating the PCS_USB registers as potentially separate from the PCS registers but used the wrong base when no PCS_USB offset has been provided. Fix the PCS_USB base used at runtime resume to prevent dereferencing a NULL pointer on platforms that do not provide a PCS_USB offset (e.g. SC7180).

AI-Powered Analysis

AILast updated: 06/30/2025, 02:27:45 UTC

Technical Analysis

CVE-2022-49848 is a vulnerability identified in the Linux kernel specifically affecting the Qualcomm QMP (Qualcomm Multi-Protocol) combo PHY driver, which handles physical layer operations for certain Qualcomm hardware components. The issue arises from a NULL pointer dereference during the runtime resume process on platforms that do not provide a PCS_USB offset, such as the SC7180 chipset. The root cause is linked to a prior commit (fc64623637da) that introduced support for treating PCS_USB registers as potentially separate from PCS registers but incorrectly used the base address when no PCS_USB offset was supplied. This incorrect base address leads to dereferencing a NULL pointer during runtime resume, which can cause the kernel to crash or behave unpredictably. The vulnerability is a logic error in the driver code that mishandles hardware register addressing, resulting in a NULL pointer dereference. While this does not directly imply arbitrary code execution, it can lead to denial of service (DoS) conditions by crashing the kernel or causing system instability on affected devices. The vulnerability affects Linux kernel versions containing the specified commit and is particularly relevant for devices using Qualcomm chipsets like the SC7180. There are no known exploits in the wild at the time of publication, and no CVSS score has been assigned yet. The fix involves correcting the PCS_USB base address used during runtime resume to prevent the NULL pointer dereference on platforms lacking a PCS_USB offset.

Potential Impact

For European organizations, the primary impact of this vulnerability is the potential for denial of service on devices running vulnerable Linux kernels with Qualcomm QMP combo PHY drivers, especially embedded systems or specialized hardware using the SC7180 or similar chipsets. This could affect network equipment, IoT devices, or industrial control systems that rely on these Linux kernel versions and Qualcomm hardware. A kernel crash caused by the NULL pointer dereference could lead to system downtime, loss of availability, and disruption of critical services. Although this vulnerability does not appear to allow privilege escalation or remote code execution, the resulting instability could be exploited as part of a broader attack chain or cause operational interruptions. Organizations with infrastructure relying on affected hardware should be aware of the risk of unexpected reboots or system failures. Given the lack of known exploits, the immediate threat is low, but the vulnerability should be addressed proactively to maintain system reliability and security.

Mitigation Recommendations

European organizations should take the following specific mitigation steps: 1) Identify all devices and systems running Linux kernels that include the affected commit or versions with Qualcomm QMP combo PHY drivers, particularly those using Qualcomm SC7180 or similar chipsets. 2) Apply the official Linux kernel patches or updates that fix the PCS_USB base address handling during runtime resume as soon as they become available from trusted Linux kernel sources or device vendors. 3) For embedded or specialized devices where kernel updates are not straightforward, coordinate with hardware vendors or maintainers to obtain patched firmware or kernel images. 4) Implement robust monitoring for kernel crashes or unexpected reboots on affected devices to detect potential exploitation or instability early. 5) Where possible, isolate critical systems using affected hardware from untrusted networks to reduce exposure. 6) Maintain up-to-date backups and recovery plans to minimize downtime in case of system failures. These steps go beyond generic advice by focusing on hardware-specific identification, patch management, and operational monitoring tailored to the nature of this vulnerability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2025-05-01T14:05:17.230Z
Cisa Enriched
false
Cvss Version
null
State
PUBLISHED

Threat ID: 682d982cc4522896dcbe4e3c

Added to database: 5/21/2025, 9:09:00 AM

Last enriched: 6/30/2025, 2:27:45 AM

Last updated: 8/11/2025, 3:04:24 AM

Views: 9

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