CyberSecBulletin
CVE-2026-63850NVD status: Analyzed

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

Published Updated By the CyberSecBulletin desk

CVE-2026-63850 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 9f5a1459ecc3195282be617639d710b54779c9dc, 139a8a52ef4349c62129703b3a3e3a6ae4d634eb, 2c350f3cd94be847ac216e1358ec7001eaaf0934 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 9f5a1459ecc3195282be617639d710b54779c9dc or 139a8a52ef4349c62129703b3a3e3a6ae4d634eb or 2c350f3cd94be847ac216e1358ec7001eaaf0934 or 8cae0ce77de492d7c31c1532a2e80c0c6e7e58cb, whichever matches your release line, or a later version.
  2. Update Linux Kernel to 6.12.91 or 6.18.33 or 7.0.10, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxb6d1a06320519ac3bfda6ce81067a1bc409b9cff up to, but not including, 9f5a1459ecc3195282be617639d710b54779c9dc; b6d1a06320519ac3bfda6ce81067a1bc409b9cff up to, but not including, 139a8a52ef4349c62129703b3a3e3a6ae4d634eb; b6d1a06320519ac3bfda6ce81067a1bc409b9cff up to, but not including, 2c350f3cd94be847ac216e1358ec7001eaaf0934; b6d1a06320519ac3bfda6ce81067a1bc409b9cff up to, but not including, 8cae0ce77de492d7c31c1532a2e80c0c6e7e58cb; 6.99f5a1459ecc3195282be617639d710b54779c9dc, 139a8a52ef4349c62129703b3a3e3a6ae4d634eb, 2c350f3cd94be847ac216e1358ec7001eaaf0934, 8cae0ce77de492d7c31c1532a2e80c0c6e7e58cb
LinuxLinux Kernel6.9 up to, but not including, 6.12.91; 6.13 up to, but not including, 6.18.33; 6.19 up to, but not including, 7.0.10; 7.16.12.91, 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 v5.0.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 49b1fbbb5a071197ee71e2d70959b1cb29bdc317)

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.