Bug 2363792 (CVE-2023-53095) - CVE-2023-53095 kernel: drm/ttm: Fix a NULL pointer dereference
Summary: CVE-2023-53095 kernel: drm/ttm: Fix a NULL pointer dereference
Keywords:
Status: NEW
Alias: CVE-2023-53095
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-02 16:05 UTC by OSIDB Bzimport
Modified: 2025-05-05 04:49 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-05-02 16:05:53 UTC
In the Linux kernel, the following vulnerability has been resolved:

drm/ttm: Fix a NULL pointer dereference

The LRU mechanism may look up a resource in the process of being removed
from an object. The locking rules here are a bit unclear but it looks
currently like res->bo assignment is protected by the LRU lock, whereas
bo->resource is protected by the object lock, while *clearing* of
bo->resource is also protected by the LRU lock. This means that if
we check that bo->resource points to the LRU resource under the LRU
lock we should be safe.
So perform that check before deciding to swap out a bo. That avoids
dereferencing a NULL bo->resource in ttm_bo_swapout().

Comment 1 Avinash Hanwate 2025-05-05 04:46:26 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025050222-CVE-2023-53095-5782@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.