CVE-2026-63853·Kernel vulnerability
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vcn: set no_user_fence for VCN v4.0 enc ring VCN encoder and decoder rings do not support 64-bit user fence writes, reject CS submissions with user fences. (cherry picked from commit fd852c048b46f9825e904a4f3f4538fe9d8827d9)
- Severity
- high
- Software
- Kernel
- Fixed in
- 7.0.10
- Published
Affected versions
From: 6.19
Until: 7.0.10
Fixed in: 7.0.10
How to fix this CVE
Update your Linux kernel to version 7.0.10 or later to resolve a local privilege escalation vulnerability affecting AMD GPU VCN encoder rings. The vulnerability stems from improper handling of 64-bit user fence writes on VCN v4.0 hardware; the patch adds validation to reject unsafe command submissions. Prioritize this update for systems running kernels 6.19 through 7.0.9 with AMD RDNA or RDNA2 GPUs.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check kernel version with `uname -r` and verify it falls within 6.19.x to 7.0.9 range
- Step 2: Confirm AMD GPU presence with `lspci | grep -i amd` and check for VCN encoder usage via `ps aux | grep -i vcn` or `dmesg | grep -i vcn`
- Step 3: Search kernel logs for VCN-related errors with `dmesg | grep -i 'vcn\|fence\|submission'` to identify failed encode operations
- Step 4: After patching, verify with `uname -r` that kernel version is 7.0.10 or later and reboot if necessary
FAQ
What is CVE-2026-63853?
This vulnerability allows local users to trigger a kernel crash or potential privilege escalation through improper validation of 64-bit user fence writes in AMD GPU VCN v4.0 encoder command submissions. The flaw permits rejection bypass for unsafe compute submissions on RDNA-based graphics cards.
Is CVE-2026-63853 being actively exploited?
No, this vulnerability is not currently listed in CISA's Known Exploited Vulnerabilities catalog and no public exploit code is available. However, local privilege escalation vulnerabilities targeting GPU drivers should be treated as high-priority given their potential impact.
What versions of Kernel are affected by CVE-2026-63853?
Linux kernel versions 6.19.x through 7.0.9 are vulnerable. Version 7.0.10 and later contain the fix.
How do I check if my server is vulnerable to CVE-2026-63853?
Run `uname -r` to display your kernel version, then cross-reference against 6.19-7.0.9 range. Next, confirm AMD GPU presence with `lspci | grep VGA | grep -i amd`. If both conditions are true, your system is vulnerable.
Does Defensia detect CVE-2026-63853?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server within the vulnerable version range, CVE-2026-63853 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/1286b6872de0aee1feeeaa6dbac86369806de9a5
- https://git.kernel.org/stable/c/51f694221047c84fa185be98210eb2c354ffb8c6
- https://git.kernel.org/stable/c/525cc9df654365c147ae61e5562cf599ea2257f7
- https://git.kernel.org/stable/c/6bdd2ed6458d35c368fbe9550a4d7f342abd3a92
- https://git.kernel.org/stable/c/772f83fc70b797ac88d696671780eaf175cc7f31
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-63853. Free for 1 server.
Get started free