linux-cve-announce - CVE-2024-27400: drm/amdgpu: once more fix the call oder in amdgpu_ttm

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]

Date: Mon, 13 May 2024 12:26:18 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-27400: drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2

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

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

drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2

This reverts drm/amdgpu: fix ftrace event amdgpu_bo_move always move
on same heap. The basic problem here is that after the move the old
location is simply not available any more.

Some fixes were suggested, but essentially we should call the move
notification before actually moving things because only this way we have
the correct order for DMA-buf and VM move notifications as well.

Also rework the statistic handling so that we don't update the eviction
counter before the move.

v2: add missing NULL check

The Linux kernel CVE team has assigned CVE-2024-27400 to this issue.


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

	Issue introduced in 6.8 with commit 94aeb4117343 and fixed in 6.9 with commit d3a9331a6591
	Issue introduced in 5.15.149 with commit 77bcd4ab446f
	Issue introduced in 6.1.77 with commit d443fb67ca5a
	Issue introduced in 6.6.16 with commit e7a0ee45c653
	Issue introduced in 6.7.4 with commit 1cd2b612474c

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-2024-27400
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_object.c
	drivers/gpu/drm/amd/amdgpu/amdgpu_object.h
	drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.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/d3a9331a6591e9df64791e076f6591f440af51c3