# CVE-2022-50618: mmc: meson-gx: fix return value check of mmc_add_host()

> A missing return value check in the Linux kernel MMC driver can cause a null pointer dereference and kernel crash during device removal.

- **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:** 8 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-50618, GHSA-p932-8wx4-gvmj, UBUNTU-CVE-2022-50618

## What is CVE-2022-50618?

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

mmc: meson-gx: fix return value check of mmc_add_host()

mmc_add_host() may return error, if we ignore its return value,
it will lead two issues:
1. The memory that allocated in mmc_alloc_host() is leaked.
2. In the remove() path, mmc_remove_host() will be called to
   delete device, but it's not added yet, it will lead a kernel
   crash because of null-ptr-deref in device_del().

Fix this by checking the return value and goto error path which
will call mmc_free_host().

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


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

Apply the vendor's patch.

## Is CVE-2022-50618 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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