CVE-2026-63848

Local code execution via unsupported user fences

Published Jul 19, 2026 · Updated Jul 19, 2026

Memory corruption in the AMDGPU JPEG v2.0 driver in affected Linux Kernel releases allows local users to write GPU memory via a user fence. The JPEG v2.0 ring accepts AMDGPU_CHUNK_ID_FENCE submissions through DRM_IOCTL_AMDGPU_CS even though the hardware supports only 32-bit fence writes, causing misdirected or out-of-bounds GPU writes. Reachability requires affected VCN 2.0.x AMD hardware and access to an AMDGPU render node; exploitation can disclose or corrupt mapped data, execute code, or hang the GPU and disrupt graphics.

CVSS severity7.8
High
EPSS probability0.14%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Memory corruption in the AMDGPU JPEG v2.0 driver in affected Linux Kernel releases allows local users to write GPU memory via a user fence. The JPEG v2.0 ring accepts AMDGPU_CHUNK_ID_FENCE submissions through DRM_IOCTL_AMDGPU_CS even though the hardware supports only 32-bit fence writes, causing misdirected or out-of-bounds GPU writes. Reachability requires affected VCN 2.0.x AMD hardware and access to an AMDGPU render node; exploitation can disclose or corrupt mapped data, execute code, or hang the GPU and disrupt graphics.

The record

CVE
CVE-2026-63848
Published
Jul 19, 2026
Updated
Jul 19, 2026
Vendor
The Linux Kernel Organization
Product
Linux Kernel
Classifications
Unavailable
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jul 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Jul 19, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.6
  2. Affected versionversion=6ac27241106bc946bd50032f4cd96899c6a6fe69 <2e216c2ff159b2eb1da6e9c716d727efc73c64b5
  3. Affected versionversion=6ac27241106bc946bd50032f4cd96899c6a6fe69 <41c4f3f68a343d62bd352a95ace93a11c4ad92ed
  4. Affected versionversion=6ac27241106bc946bd50032f4cd96899c6a6fe69 <b41248d1c18384835f6532e68592ee07605da283
  5. Affected versionversion=6ac27241106bc946bd50032f4cd96899c6a6fe69 <e5f612dc91650561fe2b5b76dd6d2898ec9ad480
  6. Affected versionversion=6ac27241106bc946bd50032f4cd96899c6a6fe69 <f675801889b265634aefd30aa4503fc2b9e6ce1c

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linux Kernelversion=5.6; version=6ac27241106bc946bd50032f4cd96899c6a6fe69 <2e216c2ff159b2eb1da6e9c716d727efc73c64b5; version=6ac27241106bc946bd50032f4cd96899c6a6fe69 <41c4f3f68a343d62bd352a95ace93a11c4ad92ed; version=6ac27241106bc946bd50032f4cd96899c6a6fe69 <b41248d1c18384835f6532e68592ee07605da283; version=6ac27241106bc946bd50032f4cd96899c6a6fe69 <e5f612dc91650561fe2b5b76dd6d2898ec9ad480; version=6ac27241106bc946bd50032f4cd96899c6a6fe69 <f675801889b265634aefd30aa4503fc2b9e6ce1c

Published CVSS scores

7.8LinuxCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

No sourced classifications are available.

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo