From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-68446: drm/vmwgfx: Validate vmw_surface_metadata::array_size
Date: Wed, 12 Aug 2026 09:06:09 +0900 [thread overview]
Message-ID: <2026081257-CVE-2026-68446-e066@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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.
The Linux kernel CVE team has assigned CVE-2026-68446 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.7 with commit 504901dbb0b565fcbe466b0c56f3131586df5afd and fixed in 6.6.148 with commit 5ff94e1279176b539d451e3e754fdcbd1a8d520a
Issue introduced in 5.7 with commit 504901dbb0b565fcbe466b0c56f3131586df5afd and fixed in 6.12.101 with commit 71779fe8bf403a9b3e28dc59229fa556db32d35d
Issue introduced in 5.7 with commit 504901dbb0b565fcbe466b0c56f3131586df5afd and fixed in 6.18.42 with commit b1379f0c42b88cb60b9f3757eb5d1e73ad460ed8
Issue introduced in 5.7 with commit 504901dbb0b565fcbe466b0c56f3131586df5afd and fixed in 7.1.6 with commit 6910ccaf41678f7761ba2e57d72b77d056320b4d
Issue introduced in 5.7 with commit 504901dbb0b565fcbe466b0c56f3131586df5afd and fixed in 7.2-rc5 with commit a4f55260f7f7d4dc4d0ee55063dfb0c457b77991
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-68446
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/gpu/drm/vmwgfx/vmwgfx_surface.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/5ff94e1279176b539d451e3e754fdcbd1a8d520a
https://git.kernel.org/stable/c/71779fe8bf403a9b3e28dc59229fa556db32d35d
https://git.kernel.org/stable/c/b1379f0c42b88cb60b9f3757eb5d1e73ad460ed8
https://git.kernel.org/stable/c/6910ccaf41678f7761ba2e57d72b77d056320b4d
https://git.kernel.org/stable/c/a4f55260f7f7d4dc4d0ee55063dfb0c457b77991
reply other threads:[~2026-08-12 0:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026081257-CVE-2026-68446-e066@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.