From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80883: drm/tegra: gr2d/gr3d: Initialize address register map before HOST1X client is registered
Date: Fri, 4 Sep 2026 18:46:50 +0200 [thread overview]
Message-ID: <2026090437-CVE-2026-80883-15f7@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/tegra: gr2d/gr3d: Initialize address register map before HOST1X client is registered
The host1x_client_register() function is called just prior to register map
initialization loop, making the device available to userspace. This may
result in userspace attempting to submits a job before the register map is
initialized. Address this by moving register initialization before host1x
client registration.
The Linux kernel CVE team has assigned CVE-2026-80883 to this issue.
Affected and fixed versions
===========================
Fixed in 6.6.145 with commit 6e22d5ad61cfa38aa53fab86a530113aff6a3619
Fixed in 6.12.97 with commit 5db37fd7710e74bc4df48bddab8f571d0bfc6769
Fixed in 6.18.40 with commit 40a2a91da02c434938f0ba53877984820800b5f0
Fixed in 7.1.5 with commit 3055292b8eed69553b389a609197a241df47e68e
Fixed in 7.2 with commit c4ef5ba1131346159e31f4ef858525cf377380a6
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-80883
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/tegra/gr2d.c
drivers/gpu/drm/tegra/gr3d.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/6e22d5ad61cfa38aa53fab86a530113aff6a3619
https://git.kernel.org/stable/c/5db37fd7710e74bc4df48bddab8f571d0bfc6769
https://git.kernel.org/stable/c/40a2a91da02c434938f0ba53877984820800b5f0
https://git.kernel.org/stable/c/3055292b8eed69553b389a609197a241df47e68e
https://git.kernel.org/stable/c/c4ef5ba1131346159e31f4ef858525cf377380a6
reply other threads:[~2026-09-04 16:53 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=2026090437-CVE-2026-80883-15f7@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.