CVE-2023-54005

What it actually does

Memory leak in binder_init() due to missing call to binder_alloc_shrinker_exit() on error paths after binder_alloc_shrinker_init().

Why it matters to the business

Gradual memory exhaustion on affected Linux systems using Binder IPC can lead to performance degradation, instability, or forced reboots over extended uptime.

How an attack unfolds

An attacker with local access triggers repeated binder initialization failure paths to accumulate leaked memory until system resources are depleted.

How to fix it

Upgrade the Linux kernel to a version containing commit 486dd742ba186ea333664c517d6775b06b1448ca or later stable releases that include binder_alloc_shrinker_exit().

How to confirm the fix worked

Verify presence of binder_alloc_shrinker_exit() call in binder_init() error handling paths and confirm kernel build includes the referenced commit.

Typical attack path

1. Obtain local code execution on target Linux system
2. Repeatedly trigger binder driver initialization error conditions
3. Accumulate unreleased shrinker allocations over time
4. Monitor for system-wide memory pressure or OOM events

How to detect it

Review kernel logs for repeated binder initialization failures and correlate with increasing memory usage in binder-related allocations using slabinfo or kmemleak.

What your security team should do

• Apply the kernel fix to all affected distributions immediately
• Monitor memory usage on systems exposing Binder interfaces
• Prioritize updates for long-uptime servers and embedded devices