CVE-2022-50872

What it actually does

Memory leak in realtime_counter_init() on ARM OMAP2+ platforms where the sys_clk resource allocated by clk_get() is not released on function return.

Why it matters to the business

Affected embedded Linux systems may experience gradual resource exhaustion over extended uptime, increasing risk of instability or service disruption on OMAP2+ hardware.

How an attack unfolds

An attacker triggers repeated initialization paths that invoke realtime_counter_init(), allowing the unreleased clock resource to accumulate until memory pressure leads to denial of service.

How to fix it

Apply the fix present in commit f1af17af004ca9345c6fe4d5936d87d008d26e75 or later equivalent kernel update for OMAP2+ platforms.

How to confirm the fix worked

Confirm the patch commit is present in the kernel source tree or verify the updated kernel binary no longer contains the unreleased clk_get allocation path.

Typical attack path

1. Identify or force repeated boot or hardware initialization sequences on OMAP2+ devices
2. Trigger the realtime_counter_init path without corresponding cleanup
3. Sustain the pattern to exhaust available memory

How to detect it

Review kernel logs and memory profiling output for repeated clk_get allocations without matching releases originating from realtime_counter_init during device boot or hardware events.

What your security team should do

• Prioritize patching OMAP2+ systems to the fixed commit
• Monitor memory utilization trends on affected embedded devices
• Limit exposure of unpatched devices to untrusted initialization triggers