CyberSecBulletin
CVE-2026-63853NVD status: Modified

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/vcn: set…

Published Updated By the CyberSecBulletin desk

CVE-2026-63853 is a high-severity improper input validation vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 772f83fc70b797ac88d696671780eaf175cc7f31, 525cc9df654365c147ae61e5562cf599ea2257f7, d8df8918677136b018d71d0b94a1f6b816715946 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.18% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 772f83fc70b797ac88d696671780eaf175cc7f31 or 525cc9df654365c147ae61e5562cf599ea2257f7 or d8df8918677136b018d71d0b94a1f6b816715946 or 1286b6872de0aee1feeeaa6dbac86369806de9a5, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.6.160 or 6.12.114 or 6.18.33 or 7.0.10, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux8da1170a16e4d4b49fa07d1f75ad480847ff7eca up to, but not including, 772f83fc70b797ac88d696671780eaf175cc7f31; 8da1170a16e4d4b49fa07d1f75ad480847ff7eca up to, but not including, 525cc9df654365c147ae61e5562cf599ea2257f7; 8da1170a16e4d4b49fa07d1f75ad480847ff7eca up to, but not including, d8df8918677136b018d71d0b94a1f6b816715946; 8da1170a16e4d4b49fa07d1f75ad480847ff7eca up to, but not including, 1286b6872de0aee1feeeaa6dbac86369806de9a5; 8da1170a16e4d4b49fa07d1f75ad480847ff7eca up to, but not including, 6bdd2ed6458d35c368fbe9550a4d7f342abd3a92; 8da1170a16e4d4b49fa07d1f75ad480847ff7eca up to, but not including, 51f694221047c84fa185be98210eb2c354ffb8c6; 5.19772f83fc70b797ac88d696671780eaf175cc7f31, 525cc9df654365c147ae61e5562cf599ea2257f7, d8df8918677136b018d71d0b94a1f6b816715946, 1286b6872de0aee1feeeaa6dbac86369806de9a5, 6bdd2ed6458d35c368fbe9550a4d7f342abd3a92, 51f694221047c84fa185be98210eb2c354ffb8c6
LinuxLinux Kernel5.19 up to, but not including, 6.6.160; 6.7 up to, but not including, 6.12.114; 6.13 up to, but not including, 6.18.33; 6.19 up to, but not including, 7.0.10; 7.16.6.160, 6.12.114, 6.18.33, 7.0.10

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.

Official description

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)

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Input Validation

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How developers prevent this class of flaw

  • Consider using language-theoretic security (LangSec) techniques that characterize inputs using a formal language and build recognizers for that language. This effectively requires parsing to be a distinct layer that effectively enforces a boundary between raw input and internal data representations, instead of allowing parser code to be scattered throughout the program, where it could be subject to errors or inconsistencies that create weaknesses.
  • Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
  • Understand all the potential areas where untrusted inputs can enter the product, including but not limited to: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls.

More Improper Input Validation vulnerabilities (CWE-20)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Improper Input Validation vulnerabilities

Spotted an error? Tell us.