CVE-2023-53764
BaseFortify
Publication date: 2025-12-08
Last updated on: 2025-12-08
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| qualcomm | ath12k | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in the Linux kernel's ath12k wireless driver occurs because a required lock (ab->base_lock) is not held during a specific error handling path (WBM error path) when calling the function ath12k_peer_find_by_id(). This leads to a lockdep_assert() warning and potential kernel instability or crashes. The fix involves properly handling the spin lock/unlock in the WBM error path to ensure the necessary lock is held as expected by the function.
How can this vulnerability impact me? :
This vulnerability can cause kernel warnings and potentially lead to system instability or crashes on affected devices using the ath12k wireless driver, especially under error conditions related to wireless peer identification. This may disrupt wireless network functionality and affect system reliability.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the system logs for lockdep_assert() warnings related to ath12k_peer_find_by_id(). Specifically, look for kernel messages similar to the following: "WARNING: CPU: ... at drivers/net/wireless/ath/ath12k/peer.c:71 ath12k_peer_find_by_id". You can use the command `dmesg | grep ath12k_peer_find_by_id` or `journalctl -k | grep ath12k_peer_find_by_id` to find such messages in the kernel logs.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Linux kernel to a version that includes the fix for this vulnerability, which handles the lock properly during the WBM error path in the ath12k driver. Until the update is applied, monitoring logs for the warning and avoiding workloads that trigger this error path may reduce impact.