Local GPU compromise via unsupported user fences
Published Jul 19, 2026 · Updated Jul 19, 2026
Improper user-fence handling in Linux Kernel allows local users to compromise GPU confidentiality, integrity, and availability. The JPEG v4.0.3 ring descriptor in drivers/gpu/drm/amd/amdgpu/jpeg_v4_0_3.c leaves no_user_fence unset, so command submission accepts unsupported 64-bit user-fence writes instead of rejecting them. Reachability requires low-privilege local access to a system exposing the affected AMDGPU JPEG ring; the public record does not specify the resulting read, write, or interruption primitive.
Summary
What happened
Improper user-fence handling in Linux Kernel allows local users to compromise GPU confidentiality, integrity, and availability. The JPEG v4.0.3 ring descriptor in drivers/gpu/drm/amd/amdgpu/jpeg_v4_0_3.c leaves no_user_fence unset, so command submission accepts unsupported 64-bit user-fence writes instead of rejecting them. Reachability requires low-privilege local access to a system exposing the affected AMDGPU JPEG ring; the public record does not specify the resulting read, write, or interruption primitive.
The record
- CVE
- CVE-2026-63844
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 19, 2026CVE publishedPublication date reported by the CVE source.
- 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.
- Affected versionversion=6.5
- Affected versionversion=e684e654eba9481a9f462a7bbf5c385b7d1c076e <249fa7549736de1c8e327d7ca6b32fa148a40bd6
- Affected versionversion=e684e654eba9481a9f462a7bbf5c385b7d1c076e <83e37c0987ca92f9e87789b46dd311dcf5a4a6c8
- Affected versionversion=e684e654eba9481a9f462a7bbf5c385b7d1c076e <8549b3933038e68dc61cb934b9a54223dd244a78
- Affected versionversion=e684e654eba9481a9f462a7bbf5c385b7d1c076e <b884ff67d62ef514eee9d5f605c03101c8b6bc98
- Affected versionversion=e684e654eba9481a9f462a7bbf5c385b7d1c076e <d6bd2a5fd611ec9c8a2411f084cff2435c709608
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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