# CVE-2024-46867: drm/xe/client: fix deadlock in show_meminfo()

> A deadlock in the Linux kernel's Xe GPU driver can cause a system hang, requiring a patch to fix the locking mechanism.

- **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:** 27 Sep 2024
- **Updated:** 11 May 2026
- **Also known as:** BELL-CVE-2024-46867, DEBIAN-CVE-2024-46867, GHSA-rp89-9jxh-73fw, UBUNTU-CVE-2024-46867

## What is CVE-2024-46867?

CVE-2024-46867 is a medium-severity vulnerability in Linux kernel, published on 27 Sep 2024. 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/xe/client: fix deadlock in show_meminfo()

There is a real deadlock as well as sleeping in atomic() bug in here, if
the bo put happens to be the last ref, since bo destruction wants to
grab the same spinlock and sleeping locks.  Fix that by dropping the ref
using xe_bo_put_deferred(), and moving the final commit outside of the
lock. Dropping the lock around the put is tricky since the bo can go
out of scope and delete itself from the list, making it difficult to
navigate to the next list entry.

(cherry picked from commit 0083b8e6f11d7662283a267d4ce7c966812ffd8a)

Weakness: CWE-667 (Improper Locking)

## Which versions are affected by CVE-2024-46867?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2024-46867?

Apply the vendor's patch.

## Is CVE-2024-46867 being exploited?

There is no known exploitation of CVE-2024-46867 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-2024-46867 and fix it if it is affected.

What it is: CVE-2024-46867 is a medium-severity vulnerability in Linux kernel, published on 27 Sep 2024. 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-2024-46867 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-2024-46867/ (Markdown: https://insights.sbomify.com/CVE-2024-46867/index.md)
```

## Sources

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

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