Local privilege escalation via unsupported user fences
Published Jul 19, 2026 · Updated Jul 19, 2026
Memory corruption in the AMDGPU JPEG 5.0.1 ring in Linux Kernel allows local users to write GPU addresses via a crafted fence submission. The command-submission path accepts a FENCE chunk even though that ring cannot perform 64-bit user-fence writes, causing a GPU-initiated write to attacker-selected virtual memory. Exploitation requires local render-node access and affected AMDGPU hardware; the primitive supports kernel disclosure, code execution, privilege escalation, or a GPU hang.
Summary
What happened
Memory corruption in the AMDGPU JPEG 5.0.1 ring in Linux Kernel allows local users to write GPU addresses via a crafted fence submission. The command-submission path accepts a FENCE chunk even though that ring cannot perform 64-bit user-fence writes, causing a GPU-initiated write to attacker-selected virtual memory. Exploitation requires local render-node access and affected AMDGPU hardware; the primitive supports kernel disclosure, code execution, privilege escalation, or a GPU hang.
The record
- CVE
- CVE-2026-63841
- Published
- Jul 19, 2026
- Updated
- Jul 19, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1068
- 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.14
- Affected versionversion=b8f57b69942b2faa7deee0566cc9306316fe0a74 <2f8e3da71a1b469b6e157aa3972f1448b3157840
- Affected versionversion=b8f57b69942b2faa7deee0566cc9306316fe0a74 <869ce148c0d953570f8307c3e206b47bd5d3be99
- Affected versionversion=b8f57b69942b2faa7deee0566cc9306316fe0a74 <d0f6ae14c0452be4fc3aa5cf81c74e68b3243050
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