{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2023-52916",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2023-52916"
  ],
  "published": "2024-09-06T09:08:03Z",
  "summary": "media: aspeed: Fix memory overwrite if timing is 1600x900",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nmedia: aspeed: Fix memory overwrite if timing is 1600x900\n\nWhen capturing 1600x900, system could crash when system memory usage is\ntight.\n\nThe way to reproduce this issue:\n1. Use 1600x900 to display on host\n2. Mount ISO through 'Virtual media' on OpenBMC's web\n3. Run script as below on host to do sha continuously\n  #!/bin/bash\n  while [ [1] ];\n  do\n\tfind /media -type f -printf '\"%h/%f\"\\n' | xargs sha256sum\n  done\n4. Open KVM on OpenBMC's web\n\nThe size of macro block captured is 8x8. Therefore, we should make sure\nthe height of src-buf is 8 aligned to fix this issue.",
  "severity": [
    {
      "type": "CVSS_V3",
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.120",
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2023-52916"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4c823e4027dd1d6e88c31028dec13dd19bc7b02d"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/c281355068bc258fd619c5aefd978595bede7bfe"
    }
  ],
  "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.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - The vulnerable path is reached through the local V4L2 device node (/dev/video*) via open, VIDIOC_S_DV_TIMINGS, and streaming ioctls on the BMC; the kernel does not process network packets in this driver.\nAC:L - Any non-8-aligned capture height (e.g. 1600x900) reliably allocates an undersized DMA buffer and the hardware always writes past it; an attacker who can open the device can set such timings and start streaming without depending on conditions outside their control.\nPR:L - The driver performs no capability checks; access requires only open permission on the V4L2 device (typically video-group membership), not real root or init-namespace admin privileges.\nUI:N - A local attacker with device access can open the capture device, set undersized timings, and start streaming themselves without any separate victim action.\nS:U - Impact is memory corruption within the same BMC kernel security authority that hosts the vulnerable driver; this is standard local privilege escalation, not a cross-boundary escape.\nC:H - The out-of-bounds DMA write is substantial kernel memory corruption (~25KB at 1600x900, more at other non-aligned modes) that can be leveraged for information disclosure primitives.\nI:H - Hardware DMA performs a large out-of-bounds write of capturable framebuffer data into adjacent coherent DMA/kernel memory, which is exploitable for integrity compromise and control-flow hijacking.\nA:H - The memory overwrite is documented to crash the system (kernel oops/panic) under realistic OpenBMC KVM capture workloads."
    }
  }
}