lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025120910-CVE-2025-40334-82a0@gregkh>
Date: Tue,  9 Dec 2025 13:10:16 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-40334: drm/amdgpu: validate userq buffer virtual address and size

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

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

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

drm/amdgpu: validate userq buffer virtual address and size

It needs to validate the userq object virtual address to
determine whether it is residented in a valid vm mapping.

The Linux kernel CVE team has assigned CVE-2025-40334 to this issue.


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

	Fixed in 6.17.8 with commit 5a577de86c4a1c67ca405571d6ef84e65c6897d1
	Fixed in 6.18 with commit 9e46b8bb0539d7bc9a9e7b3072fa4f6082490392

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-2025-40334
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.c
	drivers/gpu/drm/amd/amdgpu/amdgpu_userq.h
	drivers/gpu/drm/amd/amdgpu/mes_userqueue.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/5a577de86c4a1c67ca405571d6ef84e65c6897d1
	https://git.kernel.org/stable/c/9e46b8bb0539d7bc9a9e7b3072fa4f6082490392

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ