CVE Intelligence
CISA KEV High Memory corruption exploit reference

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

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, 2022 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: redhat

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • Public exploit/PoC (metasploit, github)+18
  • EPSS 8.9% (30-day exploitation probability)+14
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

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

Exploitation
Confirmed
CISA KEV, listed Aug 26, 2026
EPSS FIRST
8.86%
ahead of 95% of scored CVEs · Oct 14, 2026
Affects
Fedoraproject
Fedora and 12 more
CVSS base
7.8
High · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

CISA required action CISA

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.

US federal deadline: Aug 29, 2026 — passed 47 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Fedoraproject Fedora, Linux Linux Kernel, Netapp H300e Firmware…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. Apply the fixed version or the patch documented under Remediation.
  4. EPSS ahead of 95% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Fedoraproject Fedora version 35 Vulnerable NIST National Vulnerability Database
Linux Linux Kernel ≥ 5.8 and < 5.10.106≥ 5.11 and < 5.15.29≥ 5.16 and < 5.16.5version 5.17-rc1version 5.17-rc2version 5.17-rc3version 5.17-rc4version 5.17-rc5
and 2 more version 5.17-rc6version 5.17-rc7
Vulnerable NIST National Vulnerability Database
Netapp H300e Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H300s Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H410c Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H410s Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H500e Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H500s Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H610c Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H610s Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H615c Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H700e Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H700s Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database

Attack characteristics

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

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

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

ScoreVersionSeverityExpl.ImpactScored by
7.8 CVSS 3.1 High 1.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
7.8 CVSS 3.1 High 1.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
7.8 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP
7.1 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.2 CVSS 2.0 High 3.9 10.0 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)
Sources assign different scores within the same severity band. For prioritization we use 7.8 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-787 · Out-of-bounds Write

Other CVEs with this weakness →

CISA KEV details CISA

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

Listed
Aug 26, 2026
Federal deadline
Aug 29, 2026
passed 47 day(s) 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 reference date.

Public exploits, PoCs and detection templates

Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.

Metasploit modules
Proofs of concept on GitHub

Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 8.86%

Detection

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

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
  • Hunt retroactively in logs from before Aug 26, 2026 (KEV listing): exploitation may have started earlier.
endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · linux/linux kernel, fedoraproject/fedora, netapp/h300e firmware, netapp/h300s firmware, netapp/h410c firmware, netapp/h4
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · Published → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 13, 2026
  • CVSS changed · 7.8
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Added to CISA KEV catalog
    Aug 25, 2026 · CISA
  • 2022
  • CVE published
    Mar 25, 2022 · redhat

Source activity

Repeated readings are counted rather than listed.

  • 3× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

9 on the record

Elsewhere on this site

Fedoraproject
every CVE for this vendor
2026-08
what else CISA listed that month
CWE-787
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-98164 KVM: x86/mmu: Check write tracking in all address spaces 16d
  • High CVE-2026-98163 cgroup: Avoid iteration of dying tasks with zero refcount 19d
  • Medium CVE-2026-98162 smb/server: fix tree connection leak in smb2_tree_connect() 20d
  • Medium CVE-2026-98160 In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs… 20d
  • Medium CVE-2026-98161 Improper Check for Unusual or Exceptional Conditions in Linux Linux Kernel 20d
  • Medium CVE-2026-100079 Missing Release of Resource after Effective Lifetime in Linux Linux Kernel 20d

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.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware 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 record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2022-0995 is "Linux Kernel Out-of-Bounds Write Vulnerability", rated High. It affects Fedora (Fedoraproject); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.8 describes technical severity. EPSS 8.86% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.