linux-cve-announce - CVE-2025-71083: drm/ttm: Avoid NULL pointer deref for evicted BOs

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2026011339-CVE-2025-71083-ddb3@gregkh>
Date: Tue, 13 Jan 2026 16:35:42 +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-71083: drm/ttm: Avoid NULL pointer deref for evicted BOs

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

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

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

drm/ttm: Avoid NULL pointer deref for evicted BOs

It is possible for a BO to exist that is not currently associated with a
resource, e.g. because it has been evicted.

When devcoredump tries to read the contents of all BOs for dumping, we need
to expect this as well -- in this case, ENODATA is recorded instead of the
buffer contents.

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


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

	Issue introduced in 4.14 with commit 09ac4fcb3f255e9225967c75f5893325c116cdbe and fixed in 6.1.160 with commit 4b9944493c6d92d7b29cfd83aaf3deb842b8da79
	Issue introduced in 4.14 with commit 09ac4fcb3f255e9225967c75f5893325c116cdbe and fixed in 6.6.120 with commit 3d004f7341d4898889801ebb2ef61ffca610dd6f
	Issue introduced in 4.14 with commit 09ac4fcb3f255e9225967c75f5893325c116cdbe and fixed in 6.12.64 with commit 5a81095d3e1b521ac7cfe3b14d5f149bace3d6e0
	Issue introduced in 4.14 with commit 09ac4fcb3f255e9225967c75f5893325c116cdbe and fixed in 6.18.4 with commit b94182b3d7228aec18d069cba56d5982e9bfe1b1
	Issue introduced in 4.14 with commit 09ac4fcb3f255e9225967c75f5893325c116cdbe and fixed in 6.19-rc1 with commit 491adc6a0f9903c32b05f284df1148de39e8e644

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-71083
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/ttm/ttm_bo_vm.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/4b9944493c6d92d7b29cfd83aaf3deb842b8da79
	https://git.kernel.org/stable/c/3d004f7341d4898889801ebb2ef61ffca610dd6f
	https://git.kernel.org/stable/c/5a81095d3e1b521ac7cfe3b14d5f149bace3d6e0
	https://git.kernel.org/stable/c/b94182b3d7228aec18d069cba56d5982e9bfe1b1
	https://git.kernel.org/stable/c/491adc6a0f9903c32b05f284df1148de39e8e644