# CVE-2024-56775: drm/amd/display: Fix handling of plane refcount

> A refcount handling error in the AMD display driver can lead to double frees or memory leaks, potentially allowing attackers to execute code or cause 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:** 8 Jan 2025
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-55310, AZL-55327, BELL-CVE-2024-56775, DEBIAN-CVE-2024-56775, GHSA-pm49-6j2c-6857, ROOT-OS-DEBIAN-11-CVE-2024-56775, ROOT-OS-DEBIAN-12-CVE-2024-56775, ROOT-OS-UBUNTU-2204-CVE-2024-56775, UBUNTU-CVE-2024-56775

## What is CVE-2024-56775?

CVE-2024-56775 is a high-severity use after free vulnerability in Linux kernel, published on 8 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/amd/display: Fix handling of plane refcount

[Why]
The mechanism to backup and restore plane states doesn't maintain
refcount, which can cause issues if the refcount of the plane changes
in between backup and restore operations, such as memory leaks if the
refcount was supposed to go down, or double frees / invalid memory
accesses if the refcount was supposed to go up.

[How]
Cache and re-apply current refcount when restoring plane states.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime), CWE-415 (Double Free)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-56775 being exploited?

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

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

## Sources

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

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