From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-43444: drm/amdkfd: Unreserve bo if queue update failed
Date: Fri, 8 May 2026 16:22:53 +0200 [thread overview]
Message-ID: <2026050855-CVE-2026-43444-98ae@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/amdkfd: Unreserve bo if queue update failed
Error handling path should unreserve bo then return failed.
(cherry picked from commit c24afed7de9ecce341825d8ab55a43a254348b33)
The Linux kernel CVE team has assigned CVE-2026-43444 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.12 with commit 305cd109b761202d71f2f655ea369fe889ba1d01 and fixed in 6.12.78 with commit 781110700ada22168fbb490dd61432d23a17a5b4
Issue introduced in 6.12 with commit 305cd109b761202d71f2f655ea369fe889ba1d01 and fixed in 6.18.19 with commit 529c985da1b277b36dc99aad660f96dc70f3c467
Issue introduced in 6.12 with commit 305cd109b761202d71f2f655ea369fe889ba1d01 and fixed in 6.19.9 with commit b2b7742c465c8e3b36dc325a48abb4b9f2aaa38b
Issue introduced in 6.12 with commit 305cd109b761202d71f2f655ea369fe889ba1d01 and fixed in 7.0 with commit 2ce75a0b7e1bfddbcb9bc8aeb2e5e7fa99971acf
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-43444
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/amdkfd/kfd_process_queue_manager.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/781110700ada22168fbb490dd61432d23a17a5b4
https://git.kernel.org/stable/c/529c985da1b277b36dc99aad660f96dc70f3c467
https://git.kernel.org/stable/c/b2b7742c465c8e3b36dc325a48abb4b9f2aaa38b
https://git.kernel.org/stable/c/2ce75a0b7e1bfddbcb9bc8aeb2e5e7fa99971acf
reply other threads:[~2026-05-08 14:25 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=2026050855-CVE-2026-43444-98ae@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