# CVE-2023-53095: drm/ttm: Fix a NULL pointer dereference

> A NULL pointer dereference in the Linux kernel's TTM subsystem allows local attackers to cause a system crash via race conditions during buffer object swapping.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 May 2025
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2023-53095, DEBIAN-CVE-2023-53095, GHSA-qq4h-f4qp-wr7q, UBUNTU-CVE-2023-53095

## What is CVE-2023-53095?

CVE-2023-53095 is a medium-severity vulnerability in Linux kernel, published on 2 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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().

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2023-53095?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2023-53095?

Apply the vendor's patch.

## Is CVE-2023-53095 being exploited?

There is no known exploitation of CVE-2023-53095 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-53095 and fix it if it is affected.

What it is: CVE-2023-53095 is a medium-severity vulnerability in Linux kernel, published on 2 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-53095 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-53095/ (Markdown: https://insights.sbomify.com/CVE-2023-53095/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-53095
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-53095
- OSV: https://osv.dev/vulnerability/CVE-2023-53095

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-53095/
Summaries are generated and may contain mistakes; the official description above is the record.