How severe is CVE-2022-0995?

No CVSS score has been assigned to CVE-2022-0995 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2022-0995?

Affected package information for CVE-2022-0995 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2022-0995?

No fixed release is recorded for CVE-2022-0995 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2022-0995 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2022-0995 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Is CVE-2022-0995 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2022-0995, including 4 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-0995?

CVE-2022-0995 has an EPSS (Exploit Prediction Scoring System) score of 8.8%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2022-0995 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2022-0995 (Linux Kernel Out-of-Bounds Write Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-08-26. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-08-29. The required action was: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2022-0995?

CVE-2022-0995 is classified as Out-of-bounds Write (CWE-787). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2022-0995?

2 Metasploit modules reference CVE-2022-0995, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2022-0995 published, and has it been updated?

CVE-2022-0995 was published on March 25, 2022 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV · ACTIVELY EXPLOITED

CVE-2022-0995 — linux

CVE-2022-0995 is a Out-of-bounds Write vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-08-26) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Also known asA-227638011PUB-A-227638011

Published

Mar 25, 2022

Updated

Aug 12, 2026

Affected

13 products

Patched

See advisory

Exploits

5 known

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-08-26. Federal agencies were required to remediate by 2026-08-29.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2022-0995.

EPSS Exploitation Probability

via FIRST.org ↗

8.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

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.

Affected Products

13 products · 22 configurations

fedorafedoraproject

1 version

linux kernellinux

≥ 5.16 && < 5.16.5

1 version

5.17

h300e firmwarenetapp

all

h300s firmwarenetapp

all

h410c firmwarenetapp

all

h410s firmwarenetapp

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An out-of-bounds (OOB) memory write flaw was found in the Linux kernel’s…

github.comGithubMar 2022

An out-of-bounds (OOB) memory write flaw was found in the Linux kernel’s…

github.comMetasploitApr 2022

An out-of-bounds (OOB) memory write flaw was found in the Linux kernel’s…

packetstormsecurity.comNVDApr 2022

An out-of-bounds (OOB) memory write flaw was found in the Linux kernel’s…

packetstormsecurity.comNVDApr 2022

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2022-0995 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

There was no shipped kernel version that was seen affected by this problem.

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Source: Red Hat security advisory for CVE-2022-0995 (CC BY 4.0)

UbuntuHIGH

LSN-0111-1Ubuntu USN-7455-1Ubuntu USN-7455-2Ubuntu USN-7455-3Ubuntu USN-7459-1Ubuntu USN-7460-1Ubuntu USN-7455-4Ubuntu USN-7459-2Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-0995 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2022-0995 — linux

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2022-0995 in your dependencies?