net: mvpp2: Prevent parser TCAM memory corruption
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3f518509dedc99f0b755d2ce68d24f610e3a005a · < 46c1e23e34c9d1eaadf37f88216d9d8ce0d0bcee| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
Concurrent modifications to the mvpp2 parser’s TCAM, SRAM, and shadow SRAM can corrupt parser entries. In an observed case, mvpp2_set_rx_mode() ran on two CPUs concurrently, and the corruption caused incoming unicast traffic to be dropped. The input does not establish an attacker path, authentication requirement, or user-interaction requirement.
Engineers running Linux kernels that use the mvpp2 driver should check their versions; affected versions are not specified.