CVE-2022-48706

What it actually does

Memory leak of ifcvf_mgmt_dev structure on initialization failure path in the vDPA ifcvf driver because the error return from ifcvf_init_hw is not handled with a free before returning.

Why it matters to the business

Systems using affected Linux kernels with vDPA hardware may experience gradual memory exhaustion during repeated device initialization failures, potentially leading to reduced performance or system instability until rebooted or patched.

How an attack unfolds

An attacker with local access or the ability to induce hardware or driver initialization failures can repeatedly trigger the buggy error path, causing allocations without corresponding frees and resulting in resource exhaustion.

How to fix it

Upgrade the Linux kernel to a version containing commit 5d2cc32c1c10bd889125d2adc16a6bc3338dcd3e or later stable releases that include the proper cleanup on ifcvf init failure.

How to confirm the fix worked

Verify the running kernel contains the fix commit or is newer than the vulnerable versions; inspect source for the corrected return handling around ifcvf_mgmt_dev allocation.

Typical attack path

1. Obtain local access or ability to trigger vDPA device attach/init
2. Force or wait for ifcvf_init_hw failure condition
3. Observe ifcvf_mgmt_dev allocation without free on error return
4. Repeat to accumulate leaked memory until denial of service

How to detect it

Examine kernel logs and memory usage patterns around vDPA device initialization failures; correlate with processes or workloads that attach ifcvf devices.

What your security team should do

• Apply the kernel update containing the referenced commit as soon as possible on affected systems
• Monitor for memory pressure on hosts using vDPA/ifcvf devices
• Review device initialization logs for repeated failures that could accelerate leakage