Skip to main content

CVE-2025-22060: Vulnerability in Linux Linux

High
VulnerabilityCVE-2025-22060cvecve-2025-22060
Published: Wed Apr 16 2025 (04/16/2025, 14:12:16 UTC)
Source: CVE
Vendor/Project: Linux
Product: Linux

Description

In the Linux kernel, the following vulnerability has been resolved: net: mvpp2: Prevent parser TCAM memory corruption Protect the parser TCAM/SRAM memory, and the cached (shadow) SRAM information, from concurrent modifications. Both the TCAM and SRAM tables are indirectly accessed by configuring an index register that selects the row to read or write to. This means that operations must be atomic in order to, e.g., avoid spreading writes across multiple rows. Since the shadow SRAM array is used to find free rows in the hardware table, it must also be protected in order to avoid TOCTOU errors where multiple cores allocate the same row. This issue was detected in a situation where `mvpp2_set_rx_mode()` ran concurrently on two CPUs. In this particular case the MVPP2_PE_MAC_UC_PROMISCUOUS entry was corrupted, causing the classifier unit to drop all incoming unicast - indicated by the `rx_classifier_drops` counter.

AI-Powered Analysis

AILast updated: 07/03/2025, 20:41:54 UTC

Technical Analysis

CVE-2025-22060 is a vulnerability identified in the Linux kernel's network subsystem, specifically affecting the Marvell PPv2 (mvpp2) network driver. The vulnerability arises from a lack of atomicity in accessing and modifying the parser TCAM (Ternary Content-Addressable Memory) and SRAM (Static Random-Access Memory) tables used by the mvpp2 driver. These tables are accessed indirectly via an index register that selects the row to read or write. Without proper synchronization, concurrent modifications by multiple CPUs can cause memory corruption. The shadow SRAM array, which tracks free rows in the hardware table, is also vulnerable to race conditions leading to TOCTOU (Time-of-Check to Time-of-Use) errors where multiple cores might allocate the same row simultaneously. This issue was specifically observed when the function mvpp2_set_rx_mode() was executed concurrently on two CPUs, resulting in corruption of the MVPP2_PE_MAC_UC_PROMISCUOUS entry. The practical effect of this corruption is that the classifier unit drops all incoming unicast packets, as indicated by the rx_classifier_drops counter. This leads to a denial of service condition on the network interface. The vulnerability affects Linux kernel versions identified by the commit hash 3f518509dedc99f0b755d2ce68d24f610e3a005a and likely other versions incorporating this code. No known exploits are currently reported in the wild, and no CVSS score has been assigned yet. The root cause is a concurrency control flaw in the network driver’s memory access, which can be mitigated by ensuring atomic operations when accessing the TCAM/SRAM and shadow SRAM structures.

Potential Impact

For European organizations, this vulnerability could lead to network service disruptions on systems running affected Linux kernel versions with the mvpp2 network driver enabled. The denial of service caused by dropped unicast packets can impact critical network communications, potentially affecting servers, network appliances, or embedded systems using this driver. This is particularly relevant for organizations relying on Linux-based infrastructure in telecommunications, data centers, or industrial control systems where Marvell PPv2 hardware is deployed. The loss of network connectivity can degrade business operations, interrupt services, and reduce availability of critical applications. Although the vulnerability does not directly expose data confidentiality or integrity risks, the availability impact can be significant, especially in environments requiring high uptime and reliable network performance. European entities with large-scale Linux deployments or those in sectors such as finance, healthcare, and government should be aware of this issue to prevent potential operational disruptions.

Mitigation Recommendations

To mitigate this vulnerability, European organizations should: 1) Apply the official Linux kernel patches that enforce atomic access to the TCAM/SRAM and shadow SRAM memory structures in the mvpp2 driver as soon as they become available. 2) Audit and update Linux kernel versions on all affected systems to ensure they include the fix identified by CVE-2025-22060. 3) Implement strict concurrency controls and testing in environments using the mvpp2 driver to detect race conditions or memory corruption early. 4) Monitor network interface statistics, particularly the rx_classifier_drops counter, to detect anomalous packet drops that may indicate exploitation or related issues. 5) For critical systems, consider isolating or limiting the use of affected hardware until patched to reduce exposure. 6) Engage with hardware vendors and Linux distribution maintainers to confirm the presence of patches and coordinate timely updates. 7) Incorporate this vulnerability into vulnerability management and incident response plans to ensure rapid detection and remediation.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
Linux
Date Reserved
2024-12-29T08:45:45.812Z
Cisa Enriched
false
Cvss Version
null
State
PUBLISHED

Threat ID: 682d9831c4522896dcbe7fa0

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

Last enriched: 7/3/2025, 8:41:54 PM

Last updated: 8/17/2025, 10:39:32 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