{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-63847",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-63847"
  ],
  "published": "2026-07-19T14:05:10Z",
  "summary": "drm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring\n\nJPEG rings do not support 64-bit user fence writes, reject CS\nsubmissions with user fences.\n\n(cherry picked from commit 3216a7f4e2642bda5fd14f57586e835ae9202587)",
  "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": null,
            "compiled_filter": false
          }
        }
      }
    }
  ],
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-63847"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/63691e396105611173072ad548fc2b68831ecf23"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4d96e3cbfc66e4d66ea0096bde858e28ab62da00"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/3a96fee676fc0caf08f03ad915bec6fcd144d551"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/694fe016969c5e5a24b9e0ef7c1307eedec8ddf8"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/79405e774ede411c6b47ed41c651e40b92de64a2"
    }
  ],
  "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": 7.8,
      "cvss_v3_severity": "High",
      "scenario": "AV:L - Exploitation requires issuing DRM_IOCTL_AMDGPU_CS against /dev/dri/renderD* on a system with an affected AMD Instinct GPU (MI100/MI200); this is a local ioctl path, not reachable over the network.\nAC:L - An attacker with render-node access can deterministically submit a JPEG-ring command buffer (AMDGPU_HW_IP_VCN_JPEG) with an AMDGPU_CHUNK_ID_FENCE chunk; no race or special system state is required beyond the vulnerable hardware being present.\nPR:L - The amdgpu_cs_ioctl entry point requires only DRM render-client access (DRM_AUTH|DRM_RENDER_ALLOW), which is granted to unprivileged local users in the render/video group or cloud GPU tenants with device access\u2014not root or CAP_SYS_ADMIN.\nUI:N - Exploitation is fully programmatic via ioctl submission and does not require any action from another user or administrator.\nS:U - The corrupting GPU fence write is issued within the attacker's own DRM/GPU context and VM; impact remains within the same security authority and does not constitute a demonstrated VM escape or IOMMU boundary bypass.\nC:H - The malformed 64-bit user fence write on unsupported JPEG hardware causes GPU-initiated memory corruption at an attacker-chosen address, which can be leveraged for arbitrary memory disclosure beyond a bounded leak.\nI:H - The vulnerability gives the attacker a GPU DMA write primitive to user-specified GPU-mapped memory, enabling arbitrary data modification and potential further exploitation such as privilege escalation.\nA:H - Triggering an unsupported 64-bit fence operation on the JPEG engine can cause GPU faults, driver hangs, or kernel oops/panic, impacting system availability."
    }
  }
}