CVE-2026-63841 (GCVE-0-2026-63841)
Vulnerability from cvelistv5
Published
2026-07-19 14:04
Modified
2026-08-05 12:36
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.1 ring JPEG rings do not support 64-bit user fence writes, reject CS submissions with user fences. (cherry picked from commit 742a98e2e81702df8fe1b1eccee5223220a03dc2)
Impacted products
Vendor Product Version
Linux Linux Version: b8f57b69942b2faa7deee0566cc9306316fe0a74
Version: b8f57b69942b2faa7deee0566cc9306316fe0a74
Version: b8f57b69942b2faa7deee0566cc9306316fe0a74
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/amd/amdgpu/jpeg_v5_0_1.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "d0f6ae14c0452be4fc3aa5cf81c74e68b3243050",
              "status": "affected",
              "version": "b8f57b69942b2faa7deee0566cc9306316fe0a74",
              "versionType": "git"
            },
            {
              "lessThan": "869ce148c0d953570f8307c3e206b47bd5d3be99",
              "status": "affected",
              "version": "b8f57b69942b2faa7deee0566cc9306316fe0a74",
              "versionType": "git"
            },
            {
              "lessThan": "2f8e3da71a1b469b6e157aa3972f1448b3157840",
              "status": "affected",
              "version": "b8f57b69942b2faa7deee0566cc9306316fe0a74",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/amd/amdgpu/jpeg_v5_0_1.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.14"
            },
            {
              "lessThan": "6.14",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.33",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.0.*",
              "status": "unaffected",
              "version": "7.0.10",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.33",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.0.10",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.1 ring\n\nJPEG rings do not support 64-bit user fence writes, reject CS\nsubmissions with user fences.\n\n(cherry picked from commit 742a98e2e81702df8fe1b1eccee5223220a03dc2)"
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - Exploitation requires submitting DRM_IOCTL_AMDGPU_CS on a local /dev/dri/renderD* device node; the vulnerable JPEG v5.0.1 ring path is only reachable through this local ioctl interface, not over the network.\nAC:L - An attacker with render-node access can reliably craft an AMDGPU_CS submission with a FENCE chunk targeting the JPEG ring (ip_type=AMDGPU_HW_IP_VCN_JPEG) on VCN/JPEG 5.0.1 hardware without races or conditions outside their control.\nPR:L - DRM_IOCTL_AMDGPU_CS is gated by DRM_AUTH|DRM_RENDER_ALLOW, requiring only unprivileged local access to a render node (typical for users in the render/video group, browser GPU processes, or cloud GPU tenants), not root in the init namespace.\nUI:N - No victim interaction is required once the attacker has render-node access; exploitation is achieved entirely through crafted ioctl submissions.\nS:U - Impact is confined to the kernel/GPU driver security domain of the compromised context; this is a standard local GPU driver memory-corruption issue, not a VM escape or cross-security-authority boundary bypass.\nC:H - The unsupported 64-bit user fence path causes the JPEG engine to perform a GPU-initiated memory write to attacker-chosen GPU virtual addresses, providing a memory-corruption primitive that can be leveraged for arbitrary kernel memory disclosure in exploit chains.\nI:H - The malformed fence write is a GPU-driven arbitrary memory write to attacker-controlled GPU VA mappings (including GTT-backed system memory), constituting a memory corruption primitive exploitable for code execution or privilege escalation.\nA:H - Triggering unsupported fence operations on the JPEG engine can cause GPU hangs, engine resets, or kernel warnings/oops, resulting in denial of service affecting system availability."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T12:36:18.722Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/d0f6ae14c0452be4fc3aa5cf81c74e68b3243050"
        },
        {
          "url": "https://git.kernel.org/stable/c/869ce148c0d953570f8307c3e206b47bd5d3be99"
        },
        {
          "url": "https://git.kernel.org/stable/c/2f8e3da71a1b469b6e157aa3972f1448b3157840"
        }
      ],
      "title": "drm/amdgpu/jpeg: set no_user_fence for JPEG v5.0.1 ring",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-63841",
    "datePublished": "2026-07-19T14:04:36.591Z",
    "dateReserved": "2026-07-19T07:54:57.015Z",
    "dateUpdated": "2026-08-05T12:36:18.722Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…