# CVE-2022-50867: drm/msm/a6xx: Fix kvzalloc vs state_kcalloc usage

> A memory management error in the Linux kernel's Adreno GPU driver can lead to memory corruption or leaks, potentially causing a denial of service.

- **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:** 30 Dec 2025
- **Updated:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2022-50867, GHSA-9wcr-h5vx-c3h9, UBUNTU-CVE-2022-50867

## What is CVE-2022-50867?

CVE-2022-50867 is a high-severity memory corruption vulnerability in Linux, published on 30 Dec 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/msm/a6xx: Fix kvzalloc vs state_kcalloc usage

adreno_show_object() is a trap!  It will re-allocate the pointer it is
passed on first call, when the data is ascii85 encoded, using kvmalloc/
kvfree().  Which means the data *passed* to it must be kvmalloc'd, ie.
we cannot use the state_kcalloc() helper.

This partially reverts commit ec8f1813bf8d ("drm/msm/a6xx: Replace
kcalloc() with kvzalloc()"), but adds the missing kvfree() to fix the
memory leak that was present previously.  And adds a warning comment.

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

## Which versions are affected by CVE-2022-50867?


## How do I fix CVE-2022-50867?

Apply the vendor's patch.

## Is CVE-2022-50867 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50867 and fix it if it is affected.

What it is: CVE-2022-50867 is a high-severity memory corruption vulnerability in Linux, published on 30 Dec 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-2022-50867 in the wild and no public exploit code.

Affected product: Linux. 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-2022-50867/ (Markdown: https://insights.sbomify.com/CVE-2022-50867/index.md)
```

## Sources

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

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