Answer in brief
CVE-2023-53095 records a Medium severity (CVSS 5.5) vulnerability in drm/ttm: Fix a NULL pointer dereference. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc1:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:6.3:rc2:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=6a9b028994025f5033f10d1da30b29dfdc713384 <9ba1720f6c4a0f13c3f3cb5c28132ee75555d04f || >=6a9b028994025f5033f10d1da30b29dfdc713384 <9d9b1f9f7a72d83ebf173534e76b246349f32374 || >=6a9b028994025f5033f10d1da30b29dfdc713384 <9a9a8fe26751334b7739193a94eba741073b8a55 | 9ba1720f6c4a0f13c3f3cb5c28132ee75555d04f, 9d9b1f9f7a72d83ebf173534e76b246349f32374, 9a9a8fe26751334b7739193a94eba741073b8a55 |
| Linux/Linuxgeneric | 5.19 | Not reported |
Published upstream
May 2, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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().
Quoted source text, attributed separately from HOL analysis.