{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-53217",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-53217"
  ],
  "published": "2026-06-25T08:41:40Z",
  "summary": "net: mvpp2: sync RX data at the hardware packet offset",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnet: mvpp2: sync RX data at the hardware packet offset\n\nmvpp2 programs the RX queue packet offset, so hardware writes received\ndata at dma_addr + MVPP2_SKB_HEADROOM. The current CPU sync starts at\ndma_addr and only covers rx_bytes + MVPP2_MH_SIZE bytes, which syncs the\nunused headroom and misses the same number of bytes at the packet tail.\n\nOn non-coherent DMA systems this can leave the CPU reading stale cache\ncontents for the end of the received frame.\n\nUse dma_sync_single_range_for_cpu() with MVPP2_SKB_HEADROOM as the range\noffset so the sync covers the Marvell header and packet data actually\nwritten by hardware.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L"
    }
  ],
  "affected": [
    {
      "package": {
        "ecosystem": "Raspberry Pi OS:12",
        "name": "linux"
      },
      "versions": [
        "1:6.1.47-1+rpt4"
      ],
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-2712",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v6",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v7l",
            "binary_version": "1:6.1.47-1+rpt4"
          },
          {
            "binary_name": "linux-image-6.1.0-rpi3-rpi-v8",
            "binary_version": "1:6.1.47-1+rpt4"
          }
        ]
      },
      "database_specific": {
        "per_version": {
          "1:6.1.47-1+rpt4": {
            "linux_commit": "655fc658a15ae7a6f37103754adb39ba52a9a14e",
            "upstream_version": "6.1.47",
            "assessment": "commit ancestry (strak rule)",
            "upstream_fixed": "6.1.176",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-53217"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/60412bdd1b2576659eac23a23d2d9ff96228a643"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/19f8bc139e9b149d1e5bf75ae761d1bb8dd3e7d8"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a3ad9b5767c89531fc7dae951b51b0933dcf7051"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/bede0f481b9137d73d1cf64309cbe4b94818a5d6"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/23548007b3c66d628fc7d6b80d1e23be04ea10d9"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/a13199fa224e9f776f4005d5037df03aa9ea8f37"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/e302206ad84a407a7e5f3f6fe767ff5efaace689"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/180235600934bef6add3be637c296d6cf3272e67"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T13:16:28Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 8.6,
      "cvss_v3_severity": "High",
      "scenario": "AV:N - The vulnerable code is in the Ethernet RX path and is reached by packets received on an affected mvpp2 network interface. A remote peer can trigger it by sending network traffic to a system using this driver.\nAC:L - On affected non-coherent DMA deployments, exploitation only requires sending received frames that traverse the normal RX/NAPI path. There is no race or attacker-uncontrolled timing requirement in the vulnerable path.\nPR:N - No local privileges or authentication are required to reach the receive path. The attacker only needs network reachability to the affected interface.\nUI:N - Packet reception and processing happen automatically once the interface is up. No user action is required.\nS:U - The bug affects packet data handled within the same kernel/network-device security authority. It does not cross a VM, IOMMU, or other separate security boundary.\nC:H - The incorrect DMA sync can leave stale cache contents in the tail of received skbs, potentially exposing previous packet-buffer contents through delivery, forwarding, or reflection. Repeated remote triggering can disclose more than a few bounded bytes of network data over time.\nI:L - The CPU-visible packet tail can differ from the actual frame written by hardware, corrupting data delivered to XDP, the network stack, or applications. This is packet/data integrity loss, but not an arbitrary kernel memory write or control-flow primitive.\nA:L - An attacker can repeatedly cause corrupted received packets, leading to packet drops, protocol failures, or degraded network service. The investigated path does not indicate a kernel panic, hang, or reliable full-system DoS."
    }
  }
}