In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring JPEG rings do not support… (CVE-2026-63847)
A vulnerability in the Linux kernel's AMDGPU JPEG driver was resolved by setting the no_user_fence flag for the JPEG v2.5 ring. The issue involved JPEG rings not supporting 64-bit user fence writes, leading to rejection of command submissions with user fences. This fix prevents improper handling of user fences in this component.
AI Analysis
Technical Summary
The Linux kernel AMDGPU JPEG driver had a vulnerability related to the handling of user fences on JPEG v2.5 rings. Specifically, these rings do not support 64-bit user fence writes, but the driver did not properly reject command submissions containing such fences. The vulnerability was addressed by setting the no_user_fence flag for the JPEG v2.5 ring, ensuring that command submissions with user fences are rejected. This fix was incorporated via a commit cherry-picked into the kernel source.
Potential Impact
The vulnerability could have allowed improper command submissions involving unsupported 64-bit user fence writes on the JPEG v2.5 ring, potentially leading to unexpected behavior or instability in the AMDGPU driver. No known exploits in the wild have been reported. The exact impact is not detailed in the available information.
Mitigation Recommendations
A fix has been applied in the Linux kernel by setting the no_user_fence flag for the JPEG v2.5 ring. Users should update their Linux kernel to a version that includes this commit to ensure the vulnerability is resolved. Since this is a kernel-level fix, applying the official kernel update is the recommended remediation.
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/jpeg: set no_user_fence for JPEG v2.5 ring JPEG rings do not support… (CVE-2026-63847)
Description
A vulnerability in the Linux kernel's AMDGPU JPEG driver was resolved by setting the no_user_fence flag for the JPEG v2.5 ring. The issue involved JPEG rings not supporting 64-bit user fence writes, leading to rejection of command submissions with user fences. This fix prevents improper handling of user fences in this component.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel AMDGPU JPEG driver had a vulnerability related to the handling of user fences on JPEG v2.5 rings. Specifically, these rings do not support 64-bit user fence writes, but the driver did not properly reject command submissions containing such fences. The vulnerability was addressed by setting the no_user_fence flag for the JPEG v2.5 ring, ensuring that command submissions with user fences are rejected. This fix was incorporated via a commit cherry-picked into the kernel source.
Potential Impact
The vulnerability could have allowed improper command submissions involving unsupported 64-bit user fence writes on the JPEG v2.5 ring, potentially leading to unexpected behavior or instability in the AMDGPU driver. No known exploits in the wild have been reported. The exact impact is not detailed in the available information.
Mitigation Recommendations
A fix has been applied in the Linux kernel by setting the no_user_fence flag for the JPEG v2.5 ring. Users should update their Linux kernel to a version that includes this commit to ensure the vulnerability is resolved. Since this is a kernel-level fix, applying the official kernel update is the recommended remediation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-398f-rxhj-v666
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-63847"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27ac2a4a8d5989130c8a
Added to database: 07/19/2026, 19:38:20 UTC
Last enriched: 07/19/2026, 20:16:27 UTC
Last updated: 07/20/2026, 08:36:12 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.