Skip to main content

CVE-2022-49868: Vulnerability in Linux Linux

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

Description

In the Linux kernel, the following vulnerability has been resolved: phy: ralink: mt7621-pci: add sentinel to quirks table With mt7621 soc_dev_attr fixed to register the soc as a device, kernel will experience an oops in soc_device_match_attr This quirk test was introduced in the staging driver in commit 9445ccb3714c ("staging: mt7621-pci-phy: add quirks for 'E2' revision using 'soc_device_attribute'"). The staging driver was removed, and later re-added in commit d87da32372a0 ("phy: ralink: Add PHY driver for MT7621 PCIe PHY") for kernel 5.11

AI-Powered Analysis

AILast updated: 06/30/2025, 02:42:05 UTC

Technical Analysis

CVE-2022-49868 is a vulnerability identified in the Linux kernel specifically related to the Ralink MT7621 PCIe PHY driver. The issue arises from improper handling of the soc_device_attribute registration for the MT7621 System on Chip (SoC). The vulnerability is rooted in the kernel's phy driver for Ralink devices, where a quirk test introduced in a staging driver commit (9445ccb3714c) was intended to handle 'E2' revision devices using soc_device_attribute. However, due to the removal and subsequent re-addition of the staging driver in kernel version 5.11, the soc_dev_attr was not correctly registered as a device. This misregistration leads to a kernel oops (a type of kernel panic or crash) in the soc_device_match_attr function when the kernel attempts to match device attributes. Essentially, the kernel encounters an unexpected state causing it to crash or become unstable when interacting with the MT7621 PCIe PHY hardware. The affected versions are tied to a specific commit (d87da32372a0) that reintroduced the PHY driver for MT7621 PCIe PHY. Although no known exploits are reported in the wild, the vulnerability could cause denial of service (DoS) conditions by crashing the kernel. This vulnerability is technical and low-level, affecting the Linux kernel's hardware abstraction layer for specific Ralink SoCs, which are commonly used in embedded devices such as routers and network appliances. The absence of a CVSS score indicates that this vulnerability has not yet been fully assessed for severity, but the technical details suggest a stability and availability impact rather than direct privilege escalation or data compromise.

Potential Impact

For European organizations, the primary impact of CVE-2022-49868 would be on network infrastructure devices running Linux kernels with the affected MT7621 PCIe PHY driver. This includes embedded systems such as routers, gateways, and possibly IoT devices that utilize the Ralink MT7621 SoC. A successful exploitation or triggering of this vulnerability would result in kernel crashes, leading to denial of service conditions. This could disrupt network connectivity, degrade service availability, and potentially cause operational downtime. While the vulnerability does not appear to allow for privilege escalation or data leakage, the loss of availability in critical network infrastructure could impact business continuity, especially in sectors reliant on stable network operations such as finance, telecommunications, and critical infrastructure. The lack of known exploits reduces immediate risk, but unpatched devices remain vulnerable to accidental or malicious triggering of the kernel oops. European organizations with embedded Linux devices using affected kernels should be aware of potential instability and plan for patching to maintain operational resilience.

Mitigation Recommendations

To mitigate CVE-2022-49868, European organizations should: 1) Identify and inventory all devices running Linux kernels with the affected MT7621 PCIe PHY driver, focusing on embedded systems and network appliances using Ralink MT7621 SoCs. 2) Apply kernel updates or patches that correctly register the soc_device_attribute for the MT7621 device. Since no direct patch links are provided, organizations should monitor official Linux kernel repositories and vendor advisories for the relevant fixes, particularly those related to commit d87da32372a0 and subsequent kernel versions beyond 5.11. 3) Where immediate patching is not feasible, consider isolating affected devices from critical network segments to reduce impact in case of kernel crashes. 4) Implement robust monitoring for kernel oops or crashes on devices using the MT7621 PHY driver to detect potential exploitation or instability early. 5) Engage with device vendors to confirm firmware or kernel updates addressing this vulnerability are available and plan timely deployment. 6) For custom or in-house Linux builds, ensure that the staging driver and related PHY drivers are correctly configured and tested to prevent soc_device_attribute registration issues. These steps go beyond generic advice by focusing on device identification, vendor coordination, and monitoring specific to the MT7621 PCIe PHY driver context.

Need more detailed analysis?Get Pro

Technical Details

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

Threat ID: 682d982cc4522896dcbe4eb5

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

Last enriched: 6/30/2025, 2:42:05 AM

Last updated: 8/18/2025, 11:25:10 PM

Views: 12

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