basicsecurity.net
Proof, not just disclosure.
Threats / Linux / CVE-2022-0847
CVE-2022-0847 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Linux Kernel vulnerability

Linux kernel improper initialization vulnerability allowing unprivileged local users to escalate privileges through memory corruption.

Verdict

Today item — known-exploited.

Dirty Pipe is a local privilege escalation vulnerability in the Linux kernel affecting systems where unprivileged users have shell access. Active exploitation in the wild and high EPSS score indicate significant risk to multi-user systems and containerized environments.

CISA KEV Yes · 2022-04-253EPSS 0.89063 (verify live)4Exploit Weaponized · public PoC5
01

Is it exploitable?

— the evidence, ranked above the score
Exploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
11 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-04-25).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.89063 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Linux, Kernel. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-665 Improper Initialization — weakness family: Resource / availability.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-665 · Improper InitializationResource / availability
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I gain shell access as an unprivileged local user on a Linux system.
Business
An attacker establishes initial foothold on a system through compromised credentials or application vulnerability.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I exploit the kernel's improper memory initialization to write data to read-only memory regions.
Business
The vulnerability enables direct kernel memory manipulation without requiring elevated privileges.
3

Lateral reach — past segmentation narrative 3

Attacker
I escalate my privileges to root by modifying kernel structures or executable files.
Business
The attacker gains full system control, compromising confidentiality, integrity, and availability of all hosted services and data.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • Weaponized exploit available (VulnCheck)
  • 11 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Public exploit availability
  • Catalogued by redhat (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by redhatCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.