CVE-2024-46868: firmware: qcom: uefisecapp: Fix deadlock in qcuefi_acquire()
In the Linux kernel, the following vulnerability has been resolved:
firmware: qcom: uefisecapp: Fix deadlock in qcuefi_acquire()
If the __qcuefi pointer is not set, then in the original code, we would
hold onto the lock. That means that if we tried to set it later, then
it would cause a deadlock. Drop the lock on the error path. That's
what all the callers are expecting.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel availability issue in Qualcomm UEFI secure application firmware handling. A lock could be left held after an error, creating a later deadlock. The public record does not provide CVSS, active exploitation evidence, or a standalone workaround.
Executive priority
Medium operational priority for Qualcomm-based Linux fleets; otherwise handle through normal kernel patch cycles. There is no source-backed evidence of active exploitation or broad remote exposure.
Technical view
In qcuefi_acquire(), when the __qcuefi pointer was unset, the error path retained a lock. Later attempts to set that pointer could deadlock. The fix changes the error path to drop the lock, matching caller expectations.
Likely exposure
Exposure appears limited to Linux kernels in the affected version range that include or use the qcom uefisecapp firmware path. The bundle lists Linux 6.7, 6.10.11, and 6.11 as affected, but exact downstream vendor status needs confirmation.
Exploitation context
The source bundle does not cite active exploitation, public exploit code, KEV listing, attacker prerequisites, or remote reachability. Treat this as a kernel deadlock risk until vendor-specific impact details are confirmed.
Researcher notes
The record is sparse: no CVSS, CWE, exploitability analysis, or attacker model is provided. The clearest technical fact is a lock lifecycle bug in qcuefi_acquire() fixed by releasing the lock on the error path.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Check distribution or device-vendor advisories for fixed package versions.
Prioritize systems using Qualcomm firmware secure app support.
If no update is available, request vendor guidance for interim risk handling.
Track this under kernel availability and reliability patch management.
Validation and detection
Inventory deployed Linux kernel versions across affected systems.
Confirm whether qcom uefisecapp support is built, loaded, or used.
Check vendor changelogs for CVE-2024-46868 or referenced commit hashes.
Verify deployed kernels include the lock-release fix.
Review operational logs for unexplained kernel hangs on relevant platforms.
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-46868 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.