From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89553: nouveau/gem: reserve the bo in the info ioctl around the vma lookup
Date: Fri, 11 Sep 2026 21:44:02 +0200 [thread overview]
Message-ID: <2026091122-CVE-2026-89553-eebb@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
nouveau/gem: reserve the bo in the info ioctl around the vma lookup
In the non-uvmm path, there could be a race between the info lookup
finding the vma, and the gem close path closing the vma leading
to a use-after-free.
Spotted with the help of Opus 4.6.
The Linux kernel CVE team has assigned CVE-2026-89553 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.1 with commit e758a3111914af7ee4351be86f1ac0efe87ed06e and fixed in 6.12.109 with commit 208867763843aa82efcbe3b771f1b8e6c7aa820a
Issue introduced in 3.1 with commit e758a3111914af7ee4351be86f1ac0efe87ed06e and fixed in 6.18.50 with commit ff110e85837d7ecd83f36078107be240ff5ae409
Issue introduced in 3.1 with commit e758a3111914af7ee4351be86f1ac0efe87ed06e and fixed in 7.2.4 with commit e60466011ac3a6b8045e6cc3c2cbb30d58039d2e
Issue introduced in 3.1 with commit e758a3111914af7ee4351be86f1ac0efe87ed06e and fixed in 7.3-rc1 with commit 5e17160d41d92823f3379c1982e1369680c5ce4d
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-89553
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/nouveau/nouveau_gem.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/208867763843aa82efcbe3b771f1b8e6c7aa820a
https://git.kernel.org/stable/c/ff110e85837d7ecd83f36078107be240ff5ae409
https://git.kernel.org/stable/c/e60466011ac3a6b8045e6cc3c2cbb30d58039d2e
https://git.kernel.org/stable/c/5e17160d41d92823f3379c1982e1369680c5ce4d
reply other threads:[~2026-09-11 19:57 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=2026091122-CVE-2026-89553-eebb@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.