# CVE-2022-3910: Use after free in IO_uring in the Linux Kernel

> A use-after-free flaw in the Linux Kernel io_uring subsystem allows local attackers to 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:** 22 Nov 2022
- **Updated:** 21 Apr 2025
- **Also known as:** AZL-11460, DEBIAN-CVE-2022-3910, GHSA-25w9-jc8c-rx9w, UBUNTU-CVE-2022-3910

## What is CVE-2022-3910?

CVE-2022-3910 is a high-severity use after free vulnerability in Linux kernel, published on 22 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Use After Free vulnerability in Linux Kernel allows Privilege Escalation. An improper Update of Reference Count in io_uring leads to Use-After-Free and Local Privilege Escalation.
When io_msg_ring was invoked with a fixed file, it called io_fput_file() which improperly decreased its reference count (leading to Use-After-Free and Local Privilege Escalation). Fixed files are permanently registered to the ring, and should not be put separately.

We recommend upgrading past commit  https://github.com/torvalds/linux/commit/fc7222c3a9f56271fba02aabbfbae999042f1679 https://github.com/torvalds/linux/commit/fc7222c3a9f56271fba02aabbfbae999042f1679

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2022-3910 being exploited?

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

Public exploit code:

- CVE-2022-3910 (github_poc): https://github.com/veritas501/CVE-2022-3910
- 使用两种不同的角度实现对于CVE-2022-3910的利用 (github_poc): https://github.com/TLD1027/CVE-2022-3910

## 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-3910 and fix it if it is affected.

What it is: CVE-2022-3910 is a high-severity use after free vulnerability in Linux kernel, published on 22 Nov 2022. 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-3910 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-3910/ (Markdown: https://insights.sbomify.com/CVE-2022-3910/index.md)
```

## Sources

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

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