Skip to content
vulnerability

CVE-2022-0185

8.4
High
KEV · Exploited in wildEPSS 25%Patch available

A heap-based buffer overflow flaw was found in the way the legacy_parse_param function in the Filesystem Context functionality of the Linux kernel verified the supplied parameters length. An unprivileged (in case of unprivileged user namespaces enabled, otherwise needs namespaced CAP_SYS_ADMIN privilege) local user able to open a filesystem that does not support the Filesystem Context API (and thus fallbacks to legacy handling) could use this flaw to escalate their privileges on the system.

exploited
Yes, in CISA KEV since 21 Aug 2024fix by 11 Sept 2024 (CISA deadline for US federal agencies)unvetted proof-of-concept code on github
fix
Patch available see the advisory in the references
likelihood
EPSS 25.2%
Published 11 Feb 2022Analysed here 2 Nov 2026CVSS scored by CISA

do firstApply updates per vendor instructions or discontinue use of the product if updates are unavailable.

triage
server-sideruntimeWAF can block: noAV · localCWE-190· Integer OverflowCWE-191· Common Weakness

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectorlocalattack complexitylowprivileges requirednoneuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2022-0185 being exploited?

Yes. CVE-2022-0185 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2022-0185?

CVE-2022-0185 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2022-0185?

Yes. A fix has been recorded for CVE-2022-0185. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2022-0185 affect?

CVE-2022-0185 affects linux:linux_kernel, netapp:h410c_firmware, netapp:h300s_firmware, netapp:h500s_firmware, and 5 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
linux:linux_kernelnetapp:h410c_firmwarenetapp:h300s_firmwarenetapp:h500s_firmwarenetapp:h700s_firmwarenetapp:h300e_firmwarenetapp:h500e_firmwarenetapp:h700e_firmwarenetapp:h410s_firmware
affected versions
kernel
  • affected8.4

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Unvetted proof-of-concept code on GitHub: 11 GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 22 Aug 2024 (SSVC 2.0.3).

timeline

  1. 19 Jan 2022First proof-of-concept repository on GitHub (unvetted)
  2. 11 Feb 2022Published · 24 days later
  3. 21 Aug 2024Added to CISA KEV (exploited in the wild) · 921 days (about 3 years) later
  4. 22 Aug 2024CISA SSVC assessment: exploitation active · 2 days later
  5. 11 Sept 2024CISA remediation due date (US federal agencies) · 19 days later
  6. 21 Oct 2025CVE record last updated · 406 days (about 1 year) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
6 references in the CVE record: 6 links

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • PoC-in-GitHub: GitHub repositories that claim a proof of concept
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved