CVE-2026-63853: drm/amdgpu/vcn: set no_user_fence for VCN v4.0 enc ring
drm/amdgpu/vcn: set nouserfence for VCN v4.0 enc ring
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.0.10-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 7.2.12-1Fixed in 7.2.14-1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.114 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.33 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 7.0.10 - Configuration
Set no_user_fence for the VCN v4.0 encoder ring so CS submissions with user fences are rejected.
Linux kernel drm/amdgpu VCN v4.0 encoder ring no_user_fence = true
Event History
Frequently Asked Questions
What is the severity of CVE-2026-63853?
The severity of CVE-2026-63853 is rated as high with a score of 7.8.
How do I fix CVE-2026-63853?
To fix CVE-2026-63853, update to the latest version of the Linux kernel that addresses this vulnerability.
What impact does CVE-2026-63853 have?
CVE-2026-63853 allows attackers to bypass certain restrictions on user fence writes in VCN encoder and decoder rings.
Is CVE-2026-63853 present in all Linux kernel versions?
CVE-2026-63853 affects specific versions of the Linux kernel that utilize the drm/amdgpu subsystem.
Can CVE-2026-63853 lead to data corruption?
Yes, CVE-2026-63853 can potentially lead to data corruption due to improper handling of fence submissions.