dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 16 May 2022.
Linux KernelOperating system · Linux

CVE-2022-0847

HIGH · 7.8 CVSS v3.1 Published 2022-03-10
Fix available
A fix is available. Upgrade to 5.10.102 / 5.15.25 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A flaw exists in the Linux kernel's pipe buffer handling where the 'flags' member of the new pipe buffer structure was not properly initialized in copy_page_to_iter_pipe and push_pipe functions. This allows unprivileged local users to write to pages in the page cache backed by read-only files, enabling privilege escalation.

MitigationApply the Linux kernel security patch to address the uninitialized pipe buffer flags. Prioritize patching systems with untrusted local users, as exploitation requires local access but yields root privileges.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.8, < 5.10.102>= 5.15, < 5.15.25>= 5.16, < 5.16.11
FedoraOperating system
Affected:= 35
Enterprise LinuxOperating system
Affected:= 8.0
Enterprise Linux EusOperating system
Affected:= 8.2= 8.4
Enterprise Linux For Ibm Z SystemsOperating system
Affected:= 8.0
Enterprise Linux For Ibm Z Systems EusOperating system
Affected:= 8.2= 8.4
Enterprise Linux For Power Little EndianOperating system
Affected:= 8.0
Enterprise Linux For Power Little Endian EusOperating system
Affected:= 8.2= 8.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check the running kernel version
    Run `uname -r` or `cat /proc/version` to obtain the installed Linux kernel version
    Affected if The version falls within any of these ranges: 5.8 to 5.10.101, 5.15.0 to 5.15.24, or 5.16.0 to 5.16.10
  2. Compare kernel version against affected ranges
    Compare your kernel version number to the affected ranges: >= 5.8 and < 5.10.102, >= 5.15 and < 5.15.25, or >= 5.16 and < 5.16.11
    Affected if Your kernel version is within one of these three vulnerable ranges
  3. Check for available kernel updates
    On Debian/Ubuntu: `apt list --upgradable 2>/dev/null | grep linux-image`. On RHEL/Fedora: `dnf check-update` or `yum list updates`
    Affected if A newer kernel version is available that is not in the affected ranges
  4. Verify current patch status
    Check if your distribution has released patches: for RHEL/Fedora check errata or run `rpm -q --changelog kernel | head -20`. For Ubuntu/Debian check security notices
    Affected if No patch has been applied to address CVE-2022-0847

You are affected if your running Linux kernel version is 5.8 to 5.10.101, 5.15.0 to 5.15.24, or 5.16.0 to 5.16.10 and no subsequent security update has been applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.10.102 / 5.15.25 / 5.16.11 or later
Fixed in 5.10.1025.15.255.16.11
Vendor patch bugzilla.redhat.com →
Interim mitigation

Apply the Linux kernel security patch to address the uninitialized pipe buffer flags. Prioritize patching systems with untrusted local users, as exploitation requires local access but yields root privileges.

Recommended fix High confidence

Upgrade to kernel >= 5.10.102 (if on 5.8-5.10.x), >= 5.15.25 (if on 5.15.x), or >= 5.16.11 (if on 5.16.x). For enterprise distributions, apply vendor-supplied kernel updates.

  1. Identify current kernel version using `uname -r`
  2. For Enterprise Linux systems, apply available kernel updates via `dnf update kernel` or `yum update kernel` and reboot
  3. For Fedora 35, apply all pending updates via `dnf update` and reboot
  4. Verify the new kernel version loaded after reboot with `uname -r`
  5. Ensure the running kernel version is >= 5.10.102, >= 5.15.25, or >= 5.16.11 depending on your base kernel branch
Caveat Kernel upgrades may require system reboot and could introduce compatibility issues with custom kernel modules or proprietary drivers; test in staging first.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-0847 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-0847 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data