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

Linux Kernel vulnerability

Linux kernel heap-based buffer overflow in legacy_parse_param function within Filesystem Context functionality enables privilege escalation via crafted filesystem operations.

Verdict

Today item — known-exploited.

A heap buffer overflow in the Linux kernel's filesystem context parsing allows local attackers to escalate privileges. The vulnerability is triggered when opening filesystems that lack Filesystem Context API support, enabling memory corruption and code execution.

CISA KEV Yes · 2024-08-213EPSS 0.25151 (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
4 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 2024-08-21).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.25151 — 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-190 Integer Overflow — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-190 · Integer OverflowMemory safety
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 craft a malicious filesystem or mount request targeting the legacy_parse_param function to trigger a heap buffer overflow.
Business
An unprivileged local user gains kernel-level code execution, compromising system integrity and enabling full system compromise.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I exploit the memory corruption to overwrite heap structures and redirect execution flow to my payload.
Business
Attackers bypass all privilege boundaries, gaining root access and ability to persist, exfiltrate data, or deploy malware across the infrastructure.
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)
  • 4 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.