Nixpkgs security tracker

Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 3 weeks ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
net: mvpp2: sync RX data at the hardware packet offset

In the Linux kernel, the following vulnerability has been resolved: net: mvpp2: sync RX data at the hardware packet offset mvpp2 programs the RX queue packet offset, so hardware writes received data at dma_addr + MVPP2_SKB_HEADROOM. The current CPU sync starts at dma_addr and only covers rx_bytes + MVPP2_MH_SIZE bytes, which syncs the unused headroom and misses the same number of bytes at the packet tail. On non-coherent DMA systems this can leave the CPU reading stale cache contents for the end of the received frame. Use dma_sync_single_range_for_cpu() with MVPP2_SKB_HEADROOM as the range offset so the sync covers the Marvell header and packet data actually written by hardware.

Affected products

Linux
  • <5.5
  • <23548007b3c66d628fc7d6b80d1e23be04ea10d9
  • =<6.18.*
  • =<6.1.*
  • =<6.6.*
  • <60412bdd1b2576659eac23a23d2d9ff96228a643
  • =<5.15.*
  • <bede0f481b9137d73d1cf64309cbe4b94818a5d6
  • <a13199fa224e9f776f4005d5037df03aa9ea8f37
  • =<6.12.*
  • =<7.0.*
  • <a3ad9b5767c89531fc7dae951b51b0933dcf7051
  • ==5.5
  • <19f8bc139e9b149d1e5bf75ae761d1bb8dd3e7d8
  • <180235600934bef6add3be637c296d6cf3272e67
  • <e302206ad84a407a7e5f3f6fe767ff5efaace689
  • =<5.10.*
  • =<*