Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 19 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-22060, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.7.

Affected products

  • Linux · Linux

    • affected 3f518509dedc99f0b755d2ce68d24f610e3a005a – < e3711163d14d02af9005e4cdad30899c565f13fb
    • affected 3f518509dedc99f0b755d2ce68d24f610e3a005a – < b3f48a41a00d6d8d9c6fe09ae47dd21c8c1c8b03
    • affected 3f518509dedc99f0b755d2ce68d24f610e3a005a – < 5b0ae1723a7d9574ae1aee7d9cf9757a30069865
    • affected 3f518509dedc99f0b755d2ce68d24f610e3a005a – < fcbfb54a0269875cf3cd6a2bff4f85a2e0a0b552
    • affected 3f518509dedc99f0b755d2ce68d24f610e3a005a – < e64e9b6e86b39db3baa576fd73da73533b54cb2d
    • affected 3f518509dedc99f0b755d2ce68d24f610e3a005a – < 46c1e23e34c9d1eaadf37f88216d9d8ce0d0bcee
    • affected 3f518509dedc99f0b755d2ce68d24f610e3a005a – < 96844075226b49af25a69a1d084b648ec2d9b08d
  • Linux · Linux

    • affected 3.17
    • unaffected < 3.17
    • unaffected 5.15.180 – ≤ 5.15.*
    • unaffected 6.1.134 – ≤ 6.1.*
    • unaffected 6.6.87 – ≤ 6.6.*
    • unaffected 6.12.23 – ≤ 6.12.*
    • unaffected 6.13.11 – ≤ 6.13.*
    • unaffected 6.14.2 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-22060 badge
[![CVE-2025-22060](https://cveledger.app/badge/CVE-2025-22060.svg)](https://cveledger.app/cve/CVE-2025-22060)

Record last updated .