CVE REMEDIATION GUIDE
CISA KEV · Known exploitedHighFixed-version data available

CVE-2022-0847 remediation guide

Linux Kernel

A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe and push_pipe functions in the Linux kernel and could thus contain stale values. An unprivileged local user could use this flaw to write to pages in the page cache backed by read only files and as such escalate their privileges on the system.

Open CVE record
ProductLinux Kernel
Affected versionsLinux Kernel 5.17 rc6, >= 5.8 < 5.10.102, >= 5.15 < 5.15.25, >= 5.16 < 5.16.11, 35, 8.0, 8.2, 8.4, 8, 8.1, 4.0, 4.4.10.2, < 2.0, <= 12.4.2-02044
Fixed versions5.10.102, 5.15.25, 5.16.11, 2.0
Priority basisImmediate · CVSS 7.8 · EPSS 88.6%
01

Identify the affected asset

Confirm whether Linux Kernel is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: Linux Kernel 5.17 rc6, >= 5.8 < 5.10.102, >= 5.15 < 5.15.25, >= 5.16 < 5.16.11, 35, 8.0, 8.2, 8.4, 8, 8.1, 4.0, 4.4.10.2, < 2.0, <= 12.4.2-02044. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply updates per vendor instructions.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.