# CVE-2022-50812: security: Restrict CONFIG_ZERO_CALL_USED_REGS to gcc or clang > 15.0.6

> A bug in clang's zero-call-used-regs feature causes NULL pointer dereferences in the Linux kernel, leading to potential denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-50812, GHSA-r8mh-3p67-p8fm, UBUNTU-CVE-2022-50812

## What is CVE-2022-50812?

CVE-2022-50812 is a vulnerability in Linux, published on 30 Dec 2025. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

security: Restrict CONFIG_ZERO_CALL_USED_REGS to gcc or clang > 15.0.6

A bad bug in clang's implementation of -fzero-call-used-regs can result
in NULL pointer dereferences (see the links above the check for more
information). Restrict CONFIG_CC_HAS_ZERO_CALL_USED_REGS to either a
supported GCC version or a clang newer than 15.0.6, which will catch
both a theoretical 15.0.7 and the upcoming 16.0.0, which will both have
the bug fixed.

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


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

Apply the vendor's patch.

## Is CVE-2022-50812 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-50812 is a vulnerability in Linux, published on 30 Dec 2025. 
Exploitation: There is no known exploitation of CVE-2022-50812 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-50812/ (Markdown: https://insights.sbomify.com/CVE-2022-50812/index.md)
```

## Sources

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

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