linux-cve-announce - CVE-2023-53378: drm/i915/dpt: Treat the DPT BO as a framebuffer

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: <2025091856-CVE-2023-53378-3d98@gregkh>
Date: Thu, 18 Sep 2025 15:34:23 +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-53378: drm/i915/dpt: Treat the DPT BO as a framebuffer

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

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

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

drm/i915/dpt: Treat the DPT BO as a framebuffer

Currently i915_gem_object_is_framebuffer() doesn't treat the
BO containing the framebuffer's DPT as a framebuffer itself.
This means eg. that the shrinker can evict the DPT BO while
leaving the actual FB BO bound, when the DPT is allocated
from regular shmem.

That causes an immediate oops during hibernate as we
try to rewrite the PTEs inside the already evicted
DPT obj.

TODO: presumably this might also be the reason for the
DPT related display faults under heavy memory pressure,
but I'm still not sure how that would happen as the object
should be pinned by intel_dpt_pin() while in active use by
the display engine...

(cherry picked from commit 779cb5ba64ec7df80675a956c9022929514f517a)

The Linux kernel CVE team has assigned CVE-2023-53378 to this issue.


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

	Issue introduced in 6.0 with commit 0dc987b699ce4266450d407d6d79d41eab88c5d0 and fixed in 6.1.23 with commit c781c107731fc09ce4330c8c636b8446d0f72aa4
	Issue introduced in 6.0 with commit 0dc987b699ce4266450d407d6d79d41eab88c5d0 and fixed in 6.2.10 with commit 5390a02b4508416b9bee96674f141c68f89bafbc
	Issue introduced in 6.0 with commit 0dc987b699ce4266450d407d6d79d41eab88c5d0 and fixed in 6.3 with commit 3413881e1ecc3cba722a2e87ec099692eed5be28

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-53378
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/i915/display/intel_dpt.c
	drivers/gpu/drm/i915/gem/i915_gem_object.h
	drivers/gpu/drm/i915/gem/i915_gem_object_types.h


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/c781c107731fc09ce4330c8c636b8446d0f72aa4
	https://git.kernel.org/stable/c/5390a02b4508416b9bee96674f141c68f89bafbc
	https://git.kernel.org/stable/c/3413881e1ecc3cba722a2e87ec099692eed5be28