LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel KVM issue on arm64 where internal locks can be taken in the wrong order. The source indicates a circular locking dependency, which can threaten stability of affected virtualization hosts. No CVSS score, CWE, or confirmed exploitation is provided.

Executive priority

Treat this as a kernel maintenance priority for arm64 virtualization infrastructure, not as an internet-wide emergency based on current evidence. Escalate if the environment runs multi-tenant KVM workloads or if vendors later assign higher severity.

Technical view

The issue is in KVM arm64. pkvm_create_hyp_vm() could acquire kvm->lock while vcpu->mutex was already held from kvm_vcpu_ioctl(), violating KVM lock ordering. The fix protects the hyp VM handle with config_lock instead.

Likely exposure

Exposure appears limited to Linux systems using arm64 KVM paths, especially protected KVM hyp VM creation behavior. The bundle lists Linux kernel versions and stable commits but does not provide distribution-specific package names or complete backport status.

Exploitation context

The provided sources do not report active exploitation, and KEV status is false. No exploit maturity, attack prerequisites, or public weaponization evidence is included in the source bundle.

Researcher notes

Evidence supports a lock-order inversion in the KVM arm64 pKVM path. Impact details are sparse: no CVSS, CWE, exploit status, or distro advisories are included. Focus validation on code lineage, fixed commits, and vendor backports.

Mitigation direction

  • Update affected Linux kernels using vendor or stable kernel guidance.
  • Prioritize arm64 virtualization hosts running KVM or pKVM workloads.
  • Verify whether distribution kernels backported the referenced stable fixes.
  • If patching is delayed, reduce untrusted access to KVM VM creation paths.
  • Monitor Linux and distribution advisories for CVSS or impact clarification.

Validation and detection

  • Inventory Linux arm64 hosts that run KVM virtualization.
  • Compare deployed kernel versions against vendor fixed builds or stable commits.
  • Check whether pKVM or related KVM arm64 functionality is enabled.
  • Review kernel package changelogs for CVE-2024-26691 or referenced commits.
  • Confirm scanner findings with vendor backport information before escalation.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-26691 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux6211753fdfd05af9e08f54c8d0ba3ee516034878, 6211753fdfd05af9e08f54c8d0ba3ee516034878, 6211753fdfd05af9e08f54c8d0ba3ee516034878unaffected
LinuxLinux3.11, 0, 6.6.18, 6.7.6, 6.8affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.