CVE-2024-41025

What it actually does

Memory leak in the Linux kernel fastrpc driver: memory allocated to copy the audio PD daemon name during init IOCTL is never freed.

Why it matters to the business

Repeated triggering exhausts kernel memory on Linux systems, risking resource exhaustion, performance degradation, or denial of service.

How an attack unfolds

An attacker triggers the audio PD daemon attach operation via the init IOCTL call repeatedly to accumulate unfreed kernel memory allocations.

How to fix it

Update the Linux kernel to include commit 8b8b82dcf393ceaca8c88939338fd4c30b5b11b2 which adds the missing free of the allocated daemon name memory.

How to confirm the fix worked

Confirm presence of the fix by inspecting kernel source for the memory free call after the attach operation or verify running kernel contains the referenced commit.

Typical attack path

1. Obtain ability to invoke the fastrpc audio daemon init IOCTL
2. Issue repeated attach operations with daemon name data
3. Observe gradual kernel memory consumption without corresponding frees

How to detect it

Review kernel logs and memory profiling tools for repeated allocations in the fastrpc audio attach path without corresponding deallocations; no public exploitation artifacts are known.

What your security team should do

• Upgrade affected Linux kernels to a version containing the fix commit
• Monitor kernel memory usage for unexplained growth in fastrpc-related allocations
• Apply kernel updates during next maintenance window given low EPSS and no KEV listing