Threats / Linux / CVE-2022-0185
CVE-2022-0185
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
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-215EPSS 0.25151 (verify live)6Exploit Weaponized · public PoC7CVSS 8.4 (CISA)4CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit 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).
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
CVSS 8.4 (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: Linux, Kernel. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-190 Integer Overflow — weakness family: Memory safety.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 922 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution 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 board1
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’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by redhatCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.