# CVE-2022-50837: net: dsa: tag_8021q: avoid leaking ctx on dsa_tag_8021q_register() error path

> A memory leak in the Linux kernel DSA tag_8021q module allows local attackers to cause a denial of service by triggering an error path.

- **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:** 30 Dec 2025
- **Updated:** 11 May 2026
- **Also known as:** DEBIAN-CVE-2022-50837, GHSA-6jwx-qgw3-m69w, UBUNTU-CVE-2022-50837

## What is CVE-2022-50837?

CVE-2022-50837 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:

net: dsa: tag_8021q: avoid leaking ctx on dsa_tag_8021q_register() error path

If dsa_tag_8021q_setup() fails, for example due to the inability of the
device to install a VLAN, the tag_8021q context of the switch will leak.
Make sure it is freed on the error path.

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


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

Apply the vendor's patch.

## Is CVE-2022-50837 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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