# CVE-2022-50234: io_uring/af_unix: defer registered files gc to io_uring release

> A use-after-free vulnerability in the Linux kernel's io_uring and af_unix subsystems allows local attackers to potentially execute arbitrary code or escalate privileges.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 15 Sep 2025
- **Updated:** 5 Aug 2026
- **Also known as:** DEBIAN-CVE-2022-50234, GHSA-qhp4-v642-v3xp, ROOT-OS-UBUNTU-2204-CVE-2022-50234, UBUNTU-CVE-2022-50234

## What is CVE-2022-50234?

CVE-2022-50234 is a high-severity use after free vulnerability in Linux kernel, published on 15 Sep 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:

io_uring/af_unix: defer registered files gc to io_uring release

Instead of putting io_uring's registered files in unix_gc() we want it
to be done by io_uring itself. The trick here is to consider io_uring
registered files for cycle detection but not actually putting them down.
Because io_uring can't register other ring instances, this will remove
all refs to the ring file triggering the ->release path and clean up
with io_ring_ctx_free().

[axboe: add kerneldoc comment to skb, fold in skb leak fix]

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2022-50234 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-50234 is a high-severity use after free vulnerability in Linux kernel, published on 15 Sep 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-50234 in the wild and no public exploit code.

Affected product: Linux kernel. 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-50234/ (Markdown: https://insights.sbomify.com/CVE-2022-50234/index.md)
```

## Sources

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

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