# CVE-2022-50814: crypto: hisilicon/zip - fix mismatch in get/set sgl_sge_nr

> A type mismatch in the Hisilicon ZIP driver causes out-of-bounds reads, potentially leading to system crashes or privilege escalation for local attackers.

- **Severity:** Not scored
- **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:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-50814, GHSA-76g7-xjv5-wpj8, UBUNTU-CVE-2022-50814

## What is CVE-2022-50814?

CVE-2022-50814 is a 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:

crypto: hisilicon/zip - fix mismatch in get/set sgl_sge_nr

KASAN reported this Bug:

	[17619.659757] BUG: KASAN: global-out-of-bounds in param_get_int+0x34/0x60
	[17619.673193] Read of size 4 at addr fffff01332d7ed00 by task read_all/1507958
	...
	[17619.698934] The buggy address belongs to the variable:
	[17619.708371]  sgl_sge_nr+0x0/0xffffffffffffa300 [hisi_zip]

There is a mismatch in hisi_zip when get/set the variable sgl_sge_nr.
The type of sgl_sge_nr is u16, and get/set sgl_sge_nr by
param_get/set_int.

Replacing param_get/set_int to param_get/set_ushort can fix this bug.

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


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

Apply the vendor's patch.

## Is CVE-2022-50814 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-50814 is a 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-50814 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-50814/ (Markdown: https://insights.sbomify.com/CVE-2022-50814/index.md)
```

## Sources

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

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