# CVE-2021-38783: Memory corruption in n/a

> An out-of-bounds write in the Allwinner R818 Android camera driver allows attackers to cause system crashes or escalate privileges.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jan 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pw3j-7fmh-8vpr

## What is CVE-2021-38783?

CVE-2021-38783 is a high-severity memory corruption vulnerability in n/a, published on 18 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a Out-of-Bound Write in the Allwinner R818 SoC Android Q SDK V1.0 camera driver "/dev/cedar_dev" through iotcl cmd IOCTL_SET_PROC_INFO and IOCTL_COPY_PROC_INFO, which could cause a system crash or EoP.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2021-38783?

It affects 1 product.


Products: Allwinnertech Android Q Sdk.

## How do I fix CVE-2021-38783?

No fix has been published for CVE-2021-38783 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-38783 being exploited?

There is no known exploitation of CVE-2021-38783 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-38786](https://insights.sbomify.com/CVE-2021-38786/): Null dereference in n/a (high 7.5)
- [CVE-2021-38787](https://insights.sbomify.com/CVE-2021-38787/): Integer overflow in n/a (high 7.5)
- [CVE-2021-38788](https://insights.sbomify.com/CVE-2021-38788/): Denial of service in n/a (high 7.5)
- [CVE-2021-38789](https://insights.sbomify.com/CVE-2021-38789/): Missing authorization in n/a (high 7.5)
- [CVE-2021-38784](https://insights.sbomify.com/CVE-2021-38784/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-38783 and fix it if it is affected.

What it is: CVE-2021-38783 is a high-severity memory corruption vulnerability in n/a, published on 18 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-38783 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-38783/ (Markdown: https://insights.sbomify.com/CVE-2021-38783/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-38783
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-38783
- OSV: https://osv.dev/vulnerability/CVE-2021-38783

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-38783/
Summaries are generated and may contain mistakes; the official description above is the record.