{
  "schema_version": "1.6.1",
  "id": "RPI-CVE-2026-63855",
  "modified": "2026-10-09T11:39:44Z",
  "upstream": [
    "CVE-2026-63855"
  ],
  "published": "2026-07-19T14:05:10Z",
  "summary": "drm/amdgpu/vcn: set no_user_fence for VCN v2.5 enc/dec rings",
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu/vcn: set no_user_fence for VCN v2.5 enc/dec rings\n\nVCN encoder and decoder rings do not support 64-bit user fence writes,\nreject CS submissions with user fences.\n\n(cherry picked from commit efc9dd5590894109bce9a0bfe1fa5592dd6b20b1)",
  "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-63855"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/2c6fb056567efb49f8674108b86088a1cfaa86d0"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/8f0ea4524dc71c6c9ec97f2711f46e12f624140f"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/602d4c5872b25ddd4d82fb2025efb9a05b187bb3"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/5a3c6f76cab164a5d803084908d7050f649ab7f9"
    },
    {
      "type": "FIX",
      "url": "https://git.kernel.org/stable/c/4f317863a3ab212a027d8c8c3cc3af4e3fb95704"
    }
  ],
  "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 - The vulnerability is reached only through the local DRM_AMDGPU_CS ioctl on a /dev/dri/renderD* node; there is no network, Bluetooth, or physical-access attack path to the VCN command submission code.\nAC:L - On affected AMD Instinct MI100 systems, an attacker with render-node access can reliably submit a VCN enc/dec command buffer with a user-fence chunk using standard libdrm/amdgpu APIs, triggering the malformed 64-bit fence write without races or victim-dependent timing.\nPR:L - Exploitation requires opening the DRM render node and submitting GPU commands, which needs only local user privileges (typically membership in the render/video group) on multi-tenant GPU cloud instances, workstations, or containers with GPU access\u2014not root or capabilities obtainable only in the init namespace.\nUI:N - No victim interaction is required; the attacker directly crafts and submits the malicious command submission through the render node without needing another user to open files, mount filesystems, or perform any action.\nS:U - The misdirected GPU fence write corrupts memory within the attacker's own GPU virtual address space on the assigned device; it does not cross a VM, container, or IOMMU security boundary to affect another security authority.\nC:H - The bug causes GPU-initiated writes to an incorrectly decoded address, constituting out-of-bounds memory corruption that can be leveraged to read adjacent GPU-mapped buffers and disclose sensitive data from the attacker's or co-resident GPU allocations.\nI:H - The hardware fence completion write is an attacker-controlled 64-bit store to a mis-decoded GPU virtual address, providing an arbitrary GPU memory write primitive that could corrupt kernel-visible GTT mappings or GPU state for further exploitation.\nA:H - Misdirected fence writes to unmapped or invalid GPU addresses can cause GPU faults, engine hangs, or full GPU resets that deny video codec and compute service on the affected accelerator."
    }
  }
}