What is CVE-2022-0995?

CVE-2022-0995 is Linux Kernel Out-of-Bounds Write Vulnerability. The supplied enrichment data classifies it as Memory Corruption mapped to CWE-787 Out-of-bounds Write.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

56 public PoC repositories reported; 3 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with Not reported where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2022-0995 using CVSS 7.8, EPSS 10%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: Dark Caracal (). Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVhighMemory Corruptionpublic exploit

CVE-2022-0995

CVE-2022-0995 — Linux Kernel Out-of-Bounds Write Vulnerability

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2022-0995 in CISA KEV with required action: 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.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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.

Published Mar 25, 2022Updated Aug 27, 2026Sources: NVD, Linux (CNA), CISA, FIRST EPSS, Red Hat (VEX), SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Aug 26, 2026

EPSS

10%

ahead of 95% of scored CVEs

Affects

Linux

kernel

CVSS base

7.8

high · 2 sources

Remediation

The vendor's own words where we have them.

Upgrade kernel to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

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.

Federal deadline Sep 9, 2026 — passed 12 days ago

Red Hat VEX · CVE-2022-0995

fixed0affected0not affected222

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Linux	kernel	kernel 5.17 rc8	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Local

Privileges Req

Low

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.8	CVSS 3.1	high	1.8	5.9	NVD, CNA, Red Hat (VEX)
7.2	CVSS 2.0	high	3.9	10	NVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-787 · Out-of-bounds Write

Modify Memory
DoS: Crash, Exit, or Restart
Execute Unauthorized Code or Commands::

Mitigation: Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.

Weakness & attack patterns

CWE-787Out-of-bounds Write

Inferred from the weakness class — not observed against this CVE.

CAPEC-100 · Overflow BuffersCAPEC-123 · Buffer Manipulation

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Aug 26, 2026

Federal deadline

Sep 9, 2026

passed 12 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

3 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

3 more posts on this CVEShowing 5 of 8 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Monitor for scanner or exploit-pattern traffic after 56 public PoC repositories were reported.

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

Dark Caracal

hash37cabc04da36e710dd4aee8609ab7553c039a54dd085460854e9ddb49b0e703286
Public Malware Feeds · Aug 20, 2026
hashd190b349d791267a9583ba9f4a1ab0e4199d1a3abfd4dae514ed5def0754ba9471
Cisco Talos · Aug 20, 2026
hash8280502c2c6902e61fc4c02a9a81b4720688449a5bca3d89dbd1e2edd507c69a71
Cisco Talos · Aug 20, 2026
hash23a83c6bbdd7d6c09a5187338065d15f2a90a252772813cba83b9818aa56cef771
Cisco Talos · Aug 20, 2026
hash00892f276299a13721642e8a9bcbcb949a658547c6c8271866a1997b79f1e5c571
Cisco Talos · Aug 20, 2026

5 more indicators on this CVEShowing 5 of 10 · Hashes, addresses and domains from a live threat exchangeUnlock free

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 7.8 (AV:L)
Aug 27, 2026 · NVD
Added to CISA KEV catalog
Aug 26, 2026 · CISA
2024
CVE is exploited. "lions2012/Penetration_Testing_POC"
Feb 8, 2024 · SOCRadar CTI
CVE is exploited. "knd06/linux-kernel-exploitation"
Feb 5, 2024 · SOCRadar CTI
CVE is exploited. "k0mi-tg/CVE-POC"
Feb 1, 2024 · SOCRadar CTI
CVE is exploited. "1nzag/CVE-2022-0995"
Jan 3, 2024 · SOCRadar CTI
2023
CVE is exploited. "Mr-xn/Penetration_Testing_POC"
Dec 6, 2023 · SOCRadar CTI
CVE is exploited. "WhooAmii/POC_to_review"
Dec 6, 2023 · SOCRadar CTI
CVE is exploited. "bsauce/kernel-exploit-factory"
Dec 6, 2023 · SOCRadar CTI
CVE is exploited. "bsauce/kernel-security-learning"
Dec 6, 2023 · SOCRadar CTI
CVE is exploited. "khanhhdz06/linux-kernel-exploitation"
Dec 6, 2023 · SOCRadar CTI
CVE is exploited. "manas3c/CVE-POC"
Dec 6, 2023 · SOCRadar CTI
CVE is exploited. "nomi-sec/PoC-in-GitHub"
Dec 6, 2023 · SOCRadar CTI
CVE is exploited. "soosmile/POC"
Dec 6, 2023 · SOCRadar CTI
CVE is exploited. "xairy/linux-kernel-exploitation"
Dec 6, 2023 · SOCRadar CTI
CVE is exploited. "xuetusummer/Penetration_Testing_POC"
Dec 6, 2023 · SOCRadar CTI
2022
Initial · CVE published
Mar 25, 2022 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

9×Github ReposDec 6, 2023 – Jun 25, 2025 · SOCRadar CTI
8×TweetsMar 12, 2026 – Aug 29, 2026 · SOCRadar CTI
6×SVRS was changedJun 28, 2025 – Aug 27, 2026 · SOCRadar CTI
1×CVE modified by NIST: CISA KEV details updated.Aug 27, 2026 · SOCRadar CTI
1×CVE appeared in the Cve Trends.Mar 12, 2026 · SOCRadar CTI

References

11 on the record

packetstormsecurity.com/files/166770/Linux-watch_queue-Filter-Out-Of-Bounds-Write.html
Exploit, Third Party Advisory, VDB Entry, NIST, GITHUB
packetstormsecurity.com/files/166815/Watch-Queue-Out-Of-Bounds-Write.html
Exploit, Third Party Advisory, VDB Entry, NIST, GITHUB
bugzilla.redhat.com/show_bug.cgi?id=2063786
Issue Tracking, Patch, Third Party Advisory, NIST, MITRE_REFERENCES
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=93ce93587d36493f2f86921fa79921b3cba63fbb
Patch, Vendor Advisory, NIST, MITRE_REFERENCES, GITHUB
security.netapp.com/advisory/ntap-20220429-0001/
Third Party Advisory, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2022-0995
US Government Resource, NIST
access.redhat.com/security/cve/CVE-2022-0995
Vendor Advisory
www.cve.org/CVERecord?id=CVE-2022-0995
Vendor Advisory

Coverage

6 stories from the feeds we poll

1 more reports on this CVEShowing 5 of 6 · Vendor research and security press coverageUnlock free

Elsewhere on this site

Linuxevery CVE for this vendor
August 2026what else CISA listed
Memory Corruptionsame class
CWE-787other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

Only the 5 indicator(s) reported for this CVE are available; no packet-level or host-forensic artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2022-0995 is Linux Kernel Out-of-Bounds Write Vulnerability, a high vulnerability affecting kernel from Linux. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 56 public PoC repositories reported; 3 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.8 describes technical severity, while EPSS 10% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.