CVE-2022-50848

What it actually does

Failure to release allocated device structure and name string when device_register() returns an error in dio_init(), causing a memory leak.

Why it matters to the business

Repeated initialization failures in affected Linux kernel drivers can gradually exhaust kernel memory, leading to degraded performance or instability on systems using DIO hardware over long uptimes; low urgency given stable low exploit probability and no observed campaigns.

How an attack unfolds

An attacker with local access triggers repeated error paths in dio_init() by forcing device registration failures, accumulating unreleased memory until system resources are depleted; no named threat actors or ransomware use reported.

How to fix it

Update the Linux kernel to the fixed commit affe3cea6b3148fa66796a48640664822ceccd48 or later stable releases containing the release function and put_device() call in the error path of dio_init().

How to confirm the fix worked

Confirm the presence of the release function and put_device() error handling in dio_init() by inspecting the kernel source at drivers/dio/dio.c after applying the fix; test device registration error paths to verify no leaks occur.

Typical attack path

1. Obtain local access to a Linux system with the vulnerable DIO driver loaded.
2. Induce device_register() failure conditions during module initialization or hotplug events.
3. Repeat the failure path to accumulate leaked memory allocations.
4. Monitor for gradual kernel memory exhaustion impacting system stability.

How to detect it

Review kernel logs for repeated device_register failures during DIO initialization; inspect memory usage trends via slabinfo or kmemleak reports for unreleased dio device objects; no public exploitation artifacts available.

What your security team should do

• Prioritize kernel updates on systems exposing DIO devices within standard patch cycles.
• Monitor EPSS and KEV status for any future increase in exploit activity.
• Audit custom kernels or embedded devices for the presence of the unfixed dio_init() error path.