CyberSecBulletin
CVE-2022-0995Exploited in the wildNVD status: Analyzed

Linux Kernel Out-of-Bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2022-0995 is a high-severity out-of-bounds write vulnerability in kernel, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. Affected kernel versions: kernel 5.17 rc8. The record does not name a fixed version, so check the vendor advisory. CISA added it to the Known Exploited Vulnerabilities catalogue on August 26, 2026, which means attacks have been observed in the wild.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Update Linux Kernel to 5.10.106 or 5.15.29 or 5.16.5, whichever matches your release line, or a later version.
  2. CISA's 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.
  3. Read the advisory on git.kernel.org for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
Kernelkernelkernel 5.17 rc8Not stated
LinuxLinux Kernel5.8 up to, but not including, 5.10.106; 5.11 up to, but not including, 5.15.29; 5.16 up to, but not including, 5.16.5; 5.175.10.106, 5.15.29, 5.16.5
Fedora ProjectFedora35Not stated
NetAppH300e FirmwareNot specified in the recordNot stated
NetAppH300s FirmwareNot specified in the recordNot stated
NetAppH410c FirmwareNot specified in the recordNot stated
NetAppH410s FirmwareNot specified in the recordNot stated
NetAppH500e FirmwareNot specified in the recordNot stated
NetAppH500s FirmwareNot specified in the recordNot stated
NetAppH610c FirmwareNot specified in the recordNot stated
NetAppH610s FirmwareNot specified in the recordNot stated
NetAppH615c FirmwareNot specified in the recordNot stated
NetAppH700e FirmwareNot specified in the recordNot stated
NetAppH700s FirmwareNot specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.17.8HighNVD
CVSS 3.17.8HighCISA (ADP)
CVSS 2.07.2HighNVD

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Write

The product writes data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • 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.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
  3. Added to CISA's Known Exploited Vulnerabilities catalogue.
  4. Record last changed materially (score, affected products, status or references).
  5. Deadline for US federal agencies to remediate, set by CISA.

References

Patches and release notes

Technical write-ups (may include proof of concept)

Other vulnerabilities in kernel

All kernel vulnerabilities

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.