CVE-2023-52794

What it actually does

Type mismatch between param_get_int and the byte-sized max_idle variable in intel_powerclamp causes out-of-bounds memory read when the parameter is accessed via sysfs.

Why it matters to the business

Kernel module can trigger memory safety checks or crashes during routine power management parameter reads, requiring kernel updates on affected Linux systems to restore stability.

How an attack unfolds

An attacker with local access reads the max_idle sysfs parameter, causing the kernel to use the wrong getter function and read beyond the variable boundary; no widespread exploitation observed.

How to fix it

Update to Linux kernel commit 6a3866dbdcf39ac93e98708e6abced511733dc18 or later stable versions containing the param_get_byte replacement for max_idle.

How to confirm the fix worked

Confirm kernel source contains the param_get_byte change for max_idle and that KASAN no longer reports global-out-of-bounds on parameter read.

Typical attack path

1. Obtain local shell or user context on Linux system with intel_powerclamp loaded
2. Access the max_idle parameter via /sys/module/intel_powerclamp/parameters/
3. Trigger param_get_int on the byte-sized variable leading to out-of-bounds read

How to detect it

Inspect dmesg or kernel logs for KASAN global-out-of-bounds messages referencing max_idle and param_get_int; no specific post-exploitation artifacts are known.

What your security team should do

• Apply the referenced kernel commit or distribution update containing the fix
• Monitor for any powerclamp-related kernel warnings in dmesg after patching
• Review systems using intel_powerclamp for thermal management needs