From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-53375: drm/amdgpu/vce: Prevent partial address patches
Date: Sun, 19 Jul 2026 12:11:46 +0200 [thread overview]
Message-ID: <2026071946-CVE-2026-53375-58f4@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/vce: Prevent partial address patches
In the case that only one of lo/hi is valid, the patching could result
in a bad address written to in FW.
The Linux kernel CVE team has assigned CVE-2026-53375 to this issue.
Affected and fixed versions
===========================
Fixed in 6.1.175 with commit 2d66d1f5d8c0434e9a5ad21cc6eaf3a5e32141d5
Fixed in 6.6.140 with commit 944db9cfa5373f67eb94621d4c2eee572c05fa3f
Fixed in 6.12.90 with commit 0ee17150763962671f43a62ddf8f6ea1feaff438
Fixed in 6.18.32 with commit b3d1a0a45c4aec484fa2a5b060b611e3d3064470
Fixed in 7.0.9 with commit ea2c554e700b86a04534b4c24ece5844e8c5f07e
Fixed in 7.1 with commit de2a02cc28d6d5d37db07d00a9a684c754a5fd74
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-53375
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/amd/amdgpu/amdgpu_vce.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/2d66d1f5d8c0434e9a5ad21cc6eaf3a5e32141d5
https://git.kernel.org/stable/c/944db9cfa5373f67eb94621d4c2eee572c05fa3f
https://git.kernel.org/stable/c/0ee17150763962671f43a62ddf8f6ea1feaff438
https://git.kernel.org/stable/c/b3d1a0a45c4aec484fa2a5b060b611e3d3064470
https://git.kernel.org/stable/c/ea2c554e700b86a04534b4c24ece5844e8c5f07e
https://git.kernel.org/stable/c/de2a02cc28d6d5d37db07d00a9a684c754a5fd74
reply other threads:[~2026-07-19 10:13 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=2026071946-CVE-2026-53375-58f4@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.