CVE-2023-52688

What it actually does

Missing resource cleanup in the ath12k rfkill configuration error path leaves core pdev allocations unfreed when rfkill setup fails.

Why it matters to the business

WiFi driver instability or gradual resource exhaustion on affected Linux systems can lead to degraded wireless performance or crashes; low exploitability keeps overall operational risk limited despite wide kernel exposure.

How an attack unfolds

An attacker with local access triggers the rfkill config error path (for example via deliberate hardware or rfkill state manipulation) to cause repeated allocation without corresponding deallocation, resulting in resource leakage.

How to fix it

Upgrade the Linux kernel to a fixed release such as 6.7.2 or later, or apply the commit b4e593a7a22fa3c7d0550ef51c90b5c21f790aa8 (or 7bbf3b67cb49d0f8a20e64b7473923041b758211) in the stable tree; rebuild and reboot.

How to confirm the fix worked

Confirm the running kernel contains the fix by checking git log for the referenced commit or verifying version >= 6.7.2; inspect ath12k rfkill init code for the added pdev destroy call in the error path.

Typical attack path

1. Obtain local access on a system using the ath12k driver
2. Manipulate rfkill or hardware state to force the rfkill config error handler
3. Repeat to accumulate unfreed pdev resources
4. Observe driver instability or kernel memory pressure

How to detect it

Review kernel logs for ath12k rfkill-related error paths or memory allocation warnings around driver load; no widespread exploitation artifacts are known.

What your security team should do

• Prioritize kernel updates on systems using ath12k WiFi hardware within normal patch cycles
• Monitor for kernel oops or memory-pressure alerts on wireless-enabled hosts
• Apply the fix during the next scheduled maintenance window