From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43399: drm/amdgpu/userq: Fix reference leak in amdgpu_userq_wait_ioctl
Date: Fri, 8 May 2026 16:22:08 +0200 [thread overview]
Message-ID: <2026050839-CVE-2026-43399-6521@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/userq: Fix reference leak in amdgpu_userq_wait_ioctl
Drop reference to syncobj and timeline fence when aborting the ioctl due
output array being too small.
(cherry picked from commit 68951e9c3e6bb22396bc42ef2359751c8315dd27)
The Linux kernel CVE team has assigned CVE-2026-43399 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.16 with commit a292fdecd72834b3bec380baa5db1e69e7f70679 and fixed in 6.18.19 with commit 762f47e2b824383d5be65eee2c40a1269b7d50c8
Issue introduced in 6.16 with commit a292fdecd72834b3bec380baa5db1e69e7f70679 and fixed in 6.19.9 with commit 5409247d41f372bec5b141ef599f2d9f5e81b746
Issue introduced in 6.16 with commit a292fdecd72834b3bec380baa5db1e69e7f70679 and fixed in 7.0 with commit 49abfa812617a7f2d0132c70d23ac98b389c6ec1
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-43399
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_userq_fence.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/762f47e2b824383d5be65eee2c40a1269b7d50c8
https://git.kernel.org/stable/c/5409247d41f372bec5b141ef599f2d9f5e81b746
https://git.kernel.org/stable/c/49abfa812617a7f2d0132c70d23ac98b389c6ec1
reply other threads:[~2026-05-08 14:23 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=2026050839-CVE-2026-43399-6521@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox