CyberSecBulletin
CVE-2026-68446NVD status: Received

In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: Validate…

Published Updated By the CyberSecBulletin desk

CVE-2026-68446 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 e949adf2d42678fb391a41db277e2fcb12090566, 0403cec2aff8037bc246cf9a0831eb169ddcd9df, aded8463466ede7a7fbd1bbf821756c67c83e89b 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.12% 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 e949adf2d42678fb391a41db277e2fcb12090566 or 0403cec2aff8037bc246cf9a0831eb169ddcd9df or aded8463466ede7a7fbd1bbf821756c67c83e89b or 5ff94e1279176b539d451e3e754fdcbd1a8d520a, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinux504901dbb0b565fcbe466b0c56f3131586df5afd up to, but not including, e949adf2d42678fb391a41db277e2fcb12090566; 504901dbb0b565fcbe466b0c56f3131586df5afd up to, but not including, 0403cec2aff8037bc246cf9a0831eb169ddcd9df; 504901dbb0b565fcbe466b0c56f3131586df5afd up to, but not including, aded8463466ede7a7fbd1bbf821756c67c83e89b; 504901dbb0b565fcbe466b0c56f3131586df5afd up to, but not including, 5ff94e1279176b539d451e3e754fdcbd1a8d520a; 504901dbb0b565fcbe466b0c56f3131586df5afd up to, but not including, 71779fe8bf403a9b3e28dc59229fa556db32d35d; 504901dbb0b565fcbe466b0c56f3131586df5afd up to, but not including, b1379f0c42b88cb60b9f3757eb5d1e73ad460ed8; 504901dbb0b565fcbe466b0c56f3131586df5afd up to, but not including, 6910ccaf41678f7761ba2e57d72b77d056320b4d; 504901dbb0b565fcbe466b0c56f3131586df5afd up to, but not including, a4f55260f7f7d4dc4d0ee55063dfb0c457b77991; and 1 more rangese949adf2d42678fb391a41db277e2fcb12090566, 0403cec2aff8037bc246cf9a0831eb169ddcd9df, aded8463466ede7a7fbd1bbf821756c67c83e89b, 5ff94e1279176b539d451e3e754fdcbd1a8d520a, 71779fe8bf403a9b3e28dc59229fa556db32d35d, b1379f0c42b88cb60b9f3757eb5d1e73ad460ed8

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/vmwgfx: Validate vmw_surface_metadata::array_size This field comes from userspace and should be validated against specific limits depending on which Shader Model (SM) is available.

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.