All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99622: drm/amdgpu: drop the dma-buf reference when a KFD import fails
Date: Fri, 20 Nov 2026 06:50:08 +0100	[thread overview]
Message-ID: <2026112033-CVE-2026-99622-b73d@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: drop the dma-buf reference when a KFD import fails

import_obj_create() takes a reference on the dma-buf for the new kgd_mem,
but the error path after validating the BO doesn't drop it. Since the
validation reserves the BO interruptibly, an import failing with
-ERESTARTSYS leaks the exported BO with its memory, and keeps the module
in use.

Importing a 64 MiB VRAM BO in a loop while getting SIGUSR1
every 20 us and another thread changes the BO's mappings:

  INFO: 171821 imports, VRAM used before 65 MiB, after 129 MiB
  modprobe: FATAL: Module amdgpu is in use.

Drop the reference, and free the sync object and the mutex of the kgd_mem
as well. With that VRAM usage returns to 65 MiB after the same test.

(cherry picked from commit b4d1eca2729840148ff2ea957724ce764ca5a94e)

The Linux kernel CVE team has assigned CVE-2026-99622 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.7 with commit 0e2e7c5b3d712f4589b3bf0eb2988337966648b6 and fixed in 6.12.118 with commit a2654cbb6a2244d8200e0505612f03bf36af2908
	Issue introduced in 6.7 with commit 0e2e7c5b3d712f4589b3bf0eb2988337966648b6 and fixed in 6.18.64 with commit 6f300412649edf42e0eb232334a84764cd945118
	Issue introduced in 6.7 with commit 0e2e7c5b3d712f4589b3bf0eb2988337966648b6 and fixed in 7.3.5 with commit 1e65f78269a95052c2de91b4a14ee83f3e780828
	Issue introduced in 6.7 with commit 0e2e7c5b3d712f4589b3bf0eb2988337966648b6 and fixed in 7.4-rc2 with commit fb900f8bfd8a16126affd186d21001e4c6533324

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-99622
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_amdkfd_gpuvm.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/a2654cbb6a2244d8200e0505612f03bf36af2908
	https://git.kernel.org/stable/c/6f300412649edf42e0eb232334a84764cd945118
	https://git.kernel.org/stable/c/1e65f78269a95052c2de91b4a14ee83f3e780828
	https://git.kernel.org/stable/c/fb900f8bfd8a16126affd186d21001e4c6533324

                 reply	other threads:[~2026-11-20  5:54 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=2026112033-CVE-2026-99622-b73d@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.