Skip to main content
VulnerabilityPublished Updated

CVE-2025-22060: Linux kernel · net: mvpp2: Prevent parser TCAM memory corruption

Affects Linux kernelSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 10 Nov 2026, 14:48 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Apr 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

AI-suggested

A fix for this vulnerability has been implemented in the Linux kernel. Users should update to a Linux kernel version that includes this fix to prevent the concurrency issue and associated memory corruption. Since no specific fixed versions are provided, users should consult the official Linux kernel advisories or source repositories for the patch and apply it accordingly.

Description

A concurrency issue in the Linux kernel's mvpp2 network driver could cause parser TCAM memory corruption. This occurs due to unprotected concurrent modifications of TCAM/SRAM tables and their cached shadow SRAM, leading to potential data corruption and packet drops. The flaw was observed when mvpp2_set_rx_mode() executed simultaneously on two CPUs, corrupting an entry and causing the classifier to drop all incoming unicast packets.

References

Community reviews

Loading reviews…