# CVE-2022-1011: Use after free in kernel

> A local attacker can exploit a use-after-free in the Linux kernel FUSE filesystem to read unauthorized data and 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:** 18 Mar 2022
- **Updated:** 2 Aug 2024
- **Also known as:** A-226679409, AZL-9087, DEBIAN-CVE-2022-1011, GHSA-8x5v-3jgc-w6jf, OESA-2022-1593, PUB-A-226679409, SUSE-SU-2022:1611-1, UBUNTU-CVE-2022-1011

## What is CVE-2022-1011?

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

### Official description

A use-after-free flaw was found in the Linux kernel’s FUSE filesystem in the way a user triggers write(). This flaw allows a local user to gain unauthorized access to data from the FUSE filesystem, resulting in privilege escalation.

Weakness: CWE-416 (Use After Free)

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

It affects 30 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kgraft-patch-SLE12-SP5_Update_30` | SUSE:Linux Enterprise Live Patching 12 SP5 | All versions | 2-2.1 |

Products: Debian Debian Linux, Fedoraproject Fedora, Linux kernel, Netapp H300e Firmware, Netapp H300s Firmware, Netapp H410c Firmware, Netapp H410s Firmware, Netapp H500e Firmware, Netapp H500s Firmware, Netapp H700e Firmware, Netapp H700s Firmware, Oracle Communications Cloud Native Core Binding Support Function, Redhat Build of Quarkus, Redhat Codeready Linux Builder, Redhat Developer Tools, Redhat Enterprise Linux, Redhat Enterprise Linux Eus, Redhat Enterprise Linux for Ibm Z Systems, Redhat Enterprise Linux for Ibm Z Systems Eus, Redhat Enterprise Linux for Power Little Endian and 10 more.

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

Apply the vendor's patch.

## Is CVE-2022-1011 being exploited?

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

Public exploit code:

- 这个漏洞感觉只能信息泄露？ (github_poc): https://github.com/xkaneiki/CVE-2022-1011

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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