[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025091558-CVE-2023-53193-74f6@gregkh>
Date: Mon, 15 Sep 2025 16:02:47 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53193: drm/amdgpu: fix amdgpu_irq_put call trace in gmc_v10_0_hw_fini
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: fix amdgpu_irq_put call trace in gmc_v10_0_hw_fini
The gmc.ecc_irq is enabled by firmware per IFWI setting,
and the host driver is not privileged to enable/disable
the interrupt. So, it is meaningless to use the amdgpu_irq_put
function in gmc_v10_0_hw_fini, which also leads to the call
trace.
[ 82.340264] Call Trace:
[ 82.340265] <TASK>
[ 82.340269] gmc_v10_0_hw_fini+0x83/0xa0 [amdgpu]
[ 82.340447] gmc_v10_0_suspend+0xe/0x20 [amdgpu]
[ 82.340623] amdgpu_device_ip_suspend_phase2+0x127/0x1c0 [amdgpu]
[ 82.340789] amdgpu_device_ip_suspend+0x3d/0x80 [amdgpu]
[ 82.340955] amdgpu_device_pre_asic_reset+0xdd/0x2b0 [amdgpu]
[ 82.341122] amdgpu_device_gpu_recover.cold+0x4dd/0xbb2 [amdgpu]
[ 82.341359] amdgpu_debugfs_reset_work+0x4c/0x70 [amdgpu]
[ 82.341529] process_one_work+0x21d/0x3f0
[ 82.341535] worker_thread+0x1fa/0x3c0
[ 82.341538] ? process_one_work+0x3f0/0x3f0
[ 82.341540] kthread+0xff/0x130
[ 82.341544] ? kthread_complete_and_exit+0x20/0x20
[ 82.341547] ret_from_fork+0x22/0x30
The Linux kernel CVE team has assigned CVE-2023-53193 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.1.26 with commit bef774effb278ff0b65ea2dbaa1ab32ba6a1dc13 and fixed in 6.1.29 with commit 59e2439111ac2bd24ea0cecf5825cf06684b2c6c
Issue introduced in 6.2.13 with commit 56a03f64fedf49a4f81c5605167b6e7bb0300a59 and fixed in 6.2.16 with commit a7e65a1ea871e99115add88ecbcfdbacc2415f07
Issue introduced in 6.3 with commit c8b5a95b570949536a2b75cd8fc4f1de0bc60629 and fixed in 6.3.3 with commit 23febab57e345c0e66f8574c1018707e7eb6ea94
Issue introduced in 6.3 with commit c8b5a95b570949536a2b75cd8fc4f1de0bc60629 and fixed in 6.4 with commit 08c677cb0b436a96a836792bb35a8ec5de4999c2
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-2023-53193
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/gmc_v10_0.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/59e2439111ac2bd24ea0cecf5825cf06684b2c6c
https://git.kernel.org/stable/c/a7e65a1ea871e99115add88ecbcfdbacc2415f07
https://git.kernel.org/stable/c/23febab57e345c0e66f8574c1018707e7eb6ea94
https://git.kernel.org/stable/c/08c677cb0b436a96a836792bb35a8ec5de4999c2
Powered by blists - more mailing lists