[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025121634-CVE-2025-68190-e648@gregkh>
Date: Tue, 16 Dec 2025 14:43:51 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-68190: drm/amdgpu/atom: Check kcalloc() for WS buffer in amdgpu_atom_execute_table_locked()
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/atom: Check kcalloc() for WS buffer in amdgpu_atom_execute_table_locked()
kcalloc() may fail. When WS is non-zero and allocation fails, ectx.ws
remains NULL while ectx.ws_size is set, leading to a potential NULL
pointer dereference in atom_get_src_int() when accessing WS entries.
Return -ENOMEM on allocation failure to avoid the NULL dereference.
The Linux kernel CVE team has assigned CVE-2025-68190 to this issue.
Affected and fixed versions
===========================
Fixed in 6.12.58 with commit 35f3fb86bb0158a298d6834e7e110dcaf07f490c
Fixed in 6.17.8 with commit 997e28d3d00a1d30649629515e4402612921205b
Fixed in 6.18 with commit cc9a8e238e42c1f43b98c097995137d644b69245
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-68190
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/atom.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/35f3fb86bb0158a298d6834e7e110dcaf07f490c
https://git.kernel.org/stable/c/997e28d3d00a1d30649629515e4402612921205b
https://git.kernel.org/stable/c/cc9a8e238e42c1f43b98c097995137d644b69245
Powered by blists - more mailing lists