# GSD-2022-1003117: drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock is detected

> A deadlock in the Linux Kernel MSM display driver can cause a denial of service, requiring a kernel patch to resolve.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 28 Jun 2022

## What is GSD-2022-1003117?

GSD-2022-1003117 is a denial of service vulnerability in Kernel, published on 28 Jun 2022. 

### Official description

drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock is detected

This is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.
This ID is fixed in Linux Kernel version v5.17.14 by commit 47e393061049aff6818d1b9fdca7351411a23fc2, it was introduced in version v4.18 by commit 7907a0d77cb461f58045763c205a5830be72e97c. For more details please see the references link.

## Which versions are affected by GSD-2022-1003117?

1 open source package ship an affected version, including Kernel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Kernel` | Linux | All versions | None |

## How do I fix GSD-2022-1003117?

No fix has been published for GSD-2022-1003117 yet. Limit exposure of the affected software until one is available.

## Is GSD-2022-1003117 being exploited?

There is no known exploitation of GSD-2022-1003117 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GSD-2022-1003117 and fix it if it is affected.

What it is: GSD-2022-1003117 is a denial of service vulnerability in Kernel, published on 28 Jun 2022. 
Exploitation: There is no known exploitation of GSD-2022-1003117 in the wild and no public exploit code.

Affected packages and fixed versions:
- Kernel (Linux): affected all versions; no fix listed

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/GSD-2022-1003117/ (Markdown: https://insights.sbomify.com/GSD-2022-1003117/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GSD-2022-1003117

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