# CVE-2024-45015: drm/msm/dpu: move dpu_encoder's connector assignment to atomic_enable()

> A null pointer dereference in the Linux kernel's DPU driver can cause a system crash when specific display state transitions occur.

- **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:** 11 Sep 2024
- **Updated:** 11 May 2026
- **Also known as:** AZL-49176, AZL-49248, BELL-CVE-2024-45015, DEBIAN-CVE-2024-45015, GHSA-375r-hmjc-j5gg, ROOT-OS-DEBIAN-11-CVE-2024-45015, ROOT-OS-DEBIAN-12-CVE-2024-45015, ROOT-OS-UBUNTU-2204-CVE-2024-45015, UBUNTU-CVE-2024-45015

## What is CVE-2024-45015?

CVE-2024-45015 is a medium-severity vulnerability in Linux kernel, published on 11 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/msm/dpu: move dpu_encoder's connector assignment to atomic_enable()

For cases where the crtc's connectors_changed was set without enable/active
getting toggled , there is an atomic_enable() call followed by an
atomic_disable() but without an atomic_mode_set().

This results in a NULL ptr access for the dpu_encoder_get_drm_fmt() call in
the atomic_enable() as the dpu_encoder's connector was cleared in the
atomic_disable() but not re-assigned as there was no atomic_mode_set() call.

Fix the NULL ptr access by moving the assignment for atomic_enable() and also
use drm_atomic_get_new_connector_for_encoder() to get the connector from
the atomic_state.

Patchwork: https://patchwork.freedesktop.org/patch/606729/

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-45015 being exploited?

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

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

## Sources

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

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