# CVE-2022-50721: dmaengine: qcom-adm: fix wrong calling convention for prep_slave_sg

> A kernel panic occurs in the qcom-adm DMA driver due to incorrect error handling, causing a denial of service for local attackers.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-50721, GHSA-9gcm-5rwh-p2jv, ROOT-OS-UBUNTU-2204-CVE-2022-50721, UBUNTU-CVE-2022-50721

## What is CVE-2022-50721?

CVE-2022-50721 is a vulnerability in Linux, published on 24 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:

dmaengine: qcom-adm: fix wrong calling convention for prep_slave_sg

The calling convention for pre_slave_sg is to return NULL on error and
provide an error log to the system. Qcom-adm instead provide error
pointer when an error occur. This indirectly cause kernel panic for
example for the nandc driver that checks only if the pointer returned by
device_prep_slave_sg is not NULL. Returning an error pointer makes nandc
think the device_prep_slave_sg function correctly completed and makes
the kernel panics later in the code.

While nandc is the one that makes the kernel crash, it was pointed out
that the real problem is qcom-adm not following calling convention for
that function.

To fix this, drop returning error pointer and return NULL with an error
log.

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


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

Apply the vendor's patch.

## Is CVE-2022-50721 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-50721 is a vulnerability in Linux, published on 24 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-50721 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-50721/ (Markdown: https://insights.sbomify.com/CVE-2022-50721/index.md)
```

## Sources

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

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