# CVE-2022-0995: Linux Kernel Out-of-Bounds Write

> A local attacker can exploit an out-of-bounds write in the Linux kernel watch_queue subsystem to gain privileged access or cause a denial of service.

- **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:** Yes, since 26 Aug 2026 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Mar 2022
- **Updated:** 27 Aug 2026
- **Also known as:** A-227638011, AZL-9152, DEBIAN-CVE-2022-0995, GHSA-q5p3-3mpm-hppr, PUB-A-227638011, UBUNTU-CVE-2022-0995

## What is CVE-2022-0995?

CVE-2022-0995 is a high-severity memory corruption vulnerability in Fedoraproject Fedora, published on 25 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An out-of-bounds (OOB) memory write flaw was found in the Linux kernel’s watch_queue event notification subsystem. This flaw can overwrite parts of the kernel state, potentially allowing a local user to gain privileged access or cause a denial of service on the system.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 13 products.


Products: Fedoraproject Fedora, Linux kernel, Netapp H300e Firmware, Netapp H300s Firmware, Netapp H410c Firmware, Netapp H410s Firmware, Netapp H500e Firmware, Netapp H500s Firmware, Netapp H610c Firmware, Netapp H610s Firmware, Netapp H615c Firmware, Netapp H700e Firmware, Netapp H700s Firmware.

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

Apply the vendor's patch. US federal agencies must fix it by 29 Aug 2026.

## Is CVE-2022-0995 being exploited?

Yes. Attackers have exploited CVE-2022-0995 in the wild since at least 26 Aug 2026.

Public exploit code:

- CVE-2022-0995 exploit (github_poc): https://github.com/Bonfee/CVE-2022-0995
- CVE-2022-0995 exploit (github_poc): https://github.com/1nzag/CVE-2022-0995
- Реализация средств повышения привилегий в Linux (github_poc): https://github.com/AndreevSemen/CVE-2022-0995
- Watch Queue Out of Bounds Write (metasploit)
- https://github.com/A1b2rt/cve-2022-0995 (github_poc): https://github.com/A1b2rt/cve-2022-0995

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0995 is a high-severity memory corruption vulnerability in Fedoraproject Fedora, published on 25 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-0995 in the wild since at least 26 Aug 2026.

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

## Sources

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

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