Skip to main content

CVE-2022-49195: Vulnerability in Linux Linux

Medium
VulnerabilityCVE-2022-49195cvecve-2022-49195
Published: Wed Feb 26 2025 (02/26/2025, 01:55:40 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: net: dsa: fix panic on shutdown if multi-chip tree failed to probe DSA probing is atypical because a tree of devices must probe all at once, so out of N switches which call dsa_tree_setup_routing_table() during probe, for (N - 1) of them, "complete" will return false and they will exit probing early. The Nth switch will set up the whole tree on their behalf. The implication is that for (N - 1) switches, the driver binds to the device successfully, without doing anything. When the driver is bound, the ->shutdown() method may run. But if the Nth switch has failed to initialize the tree, there is nothing to do for the (N - 1) driver instances, since the slave devices have not been created, etc. Moreover, dsa_switch_shutdown() expects that the calling @ds has been in fact initialized, so it jumps at dereferencing the various data structures, which is incorrect. Avoid the ensuing NULL pointer dereferences by simply checking whether the Nth switch has previously set "ds->setup = true" for the switch which is currently shutting down. The entire setup is serialized under dsa2_mutex which we already hold.

AI-Powered Analysis

AILast updated: 06/30/2025, 03:57:29 UTC

Technical Analysis

CVE-2022-49195 is a vulnerability identified in the Linux kernel's Distributed Switch Architecture (DSA) subsystem. The DSA subsystem manages network switches by treating them as a tree of devices that must be probed simultaneously. During the probing process, out of N switches, (N - 1) switches exit early without fully initializing, while the Nth switch completes the setup for the entire tree. The vulnerability arises when the Nth switch fails to initialize the tree properly, but the driver instances for the other (N - 1) switches have already bound to their devices. These bound drivers may invoke their shutdown methods, which expect the data structures to be fully initialized. However, due to the failed initialization, these data structures are null or incomplete, leading to NULL pointer dereferences and kernel panics during shutdown. The root cause is that the shutdown method does not verify whether the switch setup was successful before dereferencing pointers. The fix involves adding a check to ensure that the switch was properly set up (i.e., "ds->setup = true") before proceeding with shutdown operations. This check is serialized under the existing dsa2_mutex to maintain thread safety. This vulnerability can cause system instability or denial of service due to kernel panics triggered during device shutdown sequences involving multi-chip DSA trees that fail to probe correctly. There are no known exploits in the wild, and no CVSS score has been assigned yet.

Potential Impact

For European organizations relying on Linux-based systems, especially those using network devices with multi-chip DSA configurations (common in enterprise networking equipment, data centers, and telecom infrastructure), this vulnerability poses a risk of system crashes and denial of service. A kernel panic during shutdown can disrupt maintenance operations, automated updates, or device restarts, potentially leading to downtime or degraded network performance. Critical infrastructure providers, cloud service operators, and enterprises with complex network topologies may experience operational interruptions. While this vulnerability does not directly enable remote code execution or privilege escalation, the resulting instability can be exploited indirectly by attackers to cause service outages or complicate incident response. The absence of known exploits reduces immediate risk, but unpatched systems remain vulnerable to accidental or malicious triggering of the bug during device shutdown or reboot cycles.

Mitigation Recommendations

European organizations should prioritize applying the Linux kernel patch that addresses CVE-2022-49195 as soon as it becomes available from their Linux distribution vendors. Given the complexity of DSA multi-chip setups, network administrators should audit their infrastructure to identify devices using DSA trees and verify kernel versions for vulnerability exposure. Implementing controlled shutdown procedures that avoid abrupt or frequent reboots of affected devices can reduce the likelihood of triggering the panic. Monitoring kernel logs for signs of NULL pointer dereferences or unexpected panics related to DSA can help detect attempts to exploit or accidentally trigger the issue. For environments where immediate patching is not feasible, isolating affected devices or using fallback network paths can mitigate operational impact. Coordination with hardware vendors to ensure firmware compatibility with patched kernels is also recommended to maintain stability.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2025-02-26T01:49:39.288Z
Cisa Enriched
false
Cvss Version
null
State
PUBLISHED

Threat ID: 682d982dc4522896dcbe5211

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

Last enriched: 6/30/2025, 3:57:29 AM

Last updated: 7/30/2025, 12:56:02 AM

Views: 10

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