CVE-2024-50190

What it actually does

Memory leak of the firmware DDP package blob during ice network driver initialization due to unnecessary full blob copy instead of topology section reuse.

Why it matters to the business

Gradual memory exhaustion on systems with Intel ice-based network adapters can degrade performance or cause instability over time, increasing operational overhead especially on high-uptime servers.

How an attack unfolds

An attacker with local access could repeatedly trigger driver initialization paths such as module reloads or device resets to accumulate leaked firmware memory; listed threat actors have targeted similar Linux kernel resource issues but this specific leak shows no known remote exploitation.

How to fix it

Update the Linux kernel to a version containing the const-correct ice_cfg_tx_topo changes and topology-section-only copy logic; apply the fix referenced in the kernel commit resolving the kmemleak in ice_init_ddp_config.

How to confirm the fix worked

Verify updated kernel source or package includes the const parameter change for ice_cfg_tx_topo and absence of full kmemdup of the DDP blob; re-run kmemleak scans post-init to confirm no recurring traces.

Typical attack path

1. Obtain local access or ability to trigger ice driver probe/init
2. Cause repeated calls to ice_init_tx_topology via resets or reloads
3. Accumulate unreleased FW blob allocations leading to memory pressure

How to detect it

Inspect kmemleak reports for ice_init_ddp_config and ice_init_tx_topology call stacks; correlate with driver probe events in kernel logs on systems with Intel ice adapters.

What your security team should do

• Prioritize kernel updates on systems using ice driver hardware
• Monitor memory metrics for ice-related allocations in production
• Review driver init logs for repeated topology configuration calls