# CVE-2024-57798: drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req()

> A race condition in the Linux kernel's DisplayPort MST driver can cause a use-after-free or null dereference, leading to a system crash.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 11 Jan 2025
- **Updated:** 11 May 2026
- **Also known as:** AZL-56223, AZL-56309, BELL-CVE-2024-57798, DEBIAN-CVE-2024-57798, GHSA-9x94-vh8x-vrhp, ROOT-OS-DEBIAN-11-CVE-2024-57798, UBUNTU-CVE-2024-57798

## What is CVE-2024-57798?

CVE-2024-57798 is a high-severity use after free vulnerability in Linux kernel, published on 11 Jan 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/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req()

While receiving an MST up request message from one thread in
drm_dp_mst_handle_up_req(), the MST topology could be removed from
another thread via drm_dp_mst_topology_mgr_set_mst(false), freeing
mst_primary and setting drm_dp_mst_topology_mgr::mst_primary to NULL.
This could lead to a NULL deref/use-after-free of mst_primary in
drm_dp_mst_handle_up_req().

Avoid the above by holding a reference for mst_primary in
drm_dp_mst_handle_up_req() while it's used.

v2: Fix kfreeing the request if getting an mst_primary reference fails.

Weakness: CWE-416 (Use After Free), CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-57798 being exploited?

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

What it is: CVE-2024-57798 is a high-severity use after free vulnerability in Linux kernel, published on 11 Jan 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-2024-57798 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-57798/ (Markdown: https://insights.sbomify.com/CVE-2024-57798/index.md)
```

## Sources

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

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