{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2023-52834",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2023-52834"
  ],
  "published": "2024-05-21T15:34:20Z",
  "summary": "atl1c: Work around the DMA RX overflow issue",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\natl1c: Work around the DMA RX overflow issue\n\nThis is based on alx driver commit 881d0327db37 (\"net: alx: Work around\nthe DMA RX overflow issue\").\n\nThe alx and atl1c drivers had RX overflow error which was why a custom\nallocator was created to avoid certain addresses. The simpler workaround\nthen created for alx driver, but not for atl1c due to lack of tester.\n\nInstead of using a custom allocator, check the allocated skb address and\nuse skb_reserve() to move away from problematic 0x...fc0 address.\n\nTested on AR8131 on Acer 4540.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
    }
  ],
  "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.64",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2023-52834"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/c29a89b23f67ee592f4dee61f9d7efbf86d60315"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/57e44ff9c2c9747b2b1a53556810b0e5192655d6"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/54a6152da4993ec8e4b53dc3cf577f5a2c829afa"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/32f08b7b430ee01ec47d730f961a3306c1c7b6fb"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/86565682e9053e5deb128193ea9e88531bbae9cf"
    }
  ],
  "database_specific": {
    "source": "https://git.kernel.org/pub/scm/linux/security/vulns.git",
    "upstream_modified": "2026-08-05T11:24:39Z",
    "severity": {
      "source": "kernel CNA",
      "cvss_v3_score": 7.5,
      "cvss_v3_severity": "High",
      "scenario": "AV:N - The atl1c RX path programs DMA buffers that are refilled from atl1c_clean_rx after packets arrive on the wired Ethernet NIC; a remote peer can send traffic that drives this refill path on an internet-facing host.\nAC:L - Sustained receive traffic reliably forces RX ring refills, and field reports show the bad 0x...fc0/0x...f80 address condition and resulting RX overflow recur within minutes under load without attacker-controlled timing tricks.\nPR:N - Triggering requires only unauthenticated frames delivered to the NIC RX ring; no local account, capabilities, or protocol authentication gate sits on this path.\nUI:N - No victim action such as mounting a device or opening a file is required; ordinary inbound network traffic is sufficient.\nS:U - Impact stays within the host kernel/network stack authority as a NIC/link failure, without a documented VM escape or IOMMU isolation bypass.\nC:N - Debugging of the same silicon issue found no overrun of skb payload contents; the failure mode is an RX FIFO overflow that stops receive, not an information-disclosure primitive.\nI:N - The bug produces RXF overflow/link loss and possible device reset rather than an attacker-controlled write to kernel memory or packet data integrity compromise.\nA:H - Once the overflow hits, the interface stops receiving and typically requires module reload or reboot to recover, fully denying network availability on the affected NIC."
    }
  }
}