CVE-2024-26966

What it actually does

Missing terminating empty element in frequency table arrays in clk qcom mmcc-apq8084 driver allows out-of-bounds memory access when tables are traversed by functions such as qcom_find_freq() or qcom_find_freq_floor().

Why it matters to the business

May cause kernel instability, crashes, or limited memory corruption on devices using the APQ8084 chipset, reducing reliability of embedded Linux and Android systems with moderate ecosystem prevalence.

How an attack unfolds

An attacker loads or triggers the mmcc-apq8084 clock driver on affected hardware, then causes repeated frequency table lookups that walk past array bounds, potentially leading to denial of service; no public exploits or named threat actor campaigns are associated with this issue.

How to fix it

Update the Linux kernel to include commit 5533686e99b04994d7c4877dc0e4282adc9444a2 or any later stable release containing the terminating array entry fix.

How to confirm the fix worked

Verify the patch by inspecting drivers/clk/qcom/mmcc-apq8084.c for empty terminating entries at the end of frequency tables and confirm successful compilation and basic clock functionality tests.

Typical attack path

1. Gain local access or trigger driver initialization on APQ8084-based system
2. Invoke clock rate selection paths that call qcom_find_freq() on the unterminated table
3. Trigger out-of-bounds read resulting in kernel panic or information exposure

How to detect it

Examine kernel logs and dmesg output for out-of-bounds warnings or panics referencing mmcc-apq8084 frequency tables; no post-exploitation artifacts are known due to the nature of the flaw.

What your security team should do

• Apply the referenced kernel commit or newer stable branch to all affected systems
• Prioritize updates on Qualcomm APQ8084 deployments given the buffer overflow family classification
• Monitor kernel logs for related stability issues until patches are deployed