CVE-2024-41066

What it actually does

Missing null skb check in ibmvnic transmit path allows memory leak when free_map and tx_buff desynchronize, risking resource exhaustion and TCP timeouts.

Why it matters to the business

Affected Linux systems using IBM virtual NICs may suffer degraded network performance or connectivity loss, with low overall urgency given absence of exploitation or ransomware use.

How an attack unfolds

An attacker triggers driver map desynchronization during packet transmission to induce repeated skb leaks, eventually disrupting TCP congestion control and causing connection timeouts.

How to fix it

Upgrade the Linux kernel to include commit 16ad1557cae582e79bb82dddd612d9bdfaa11d4c or apply the equivalent stable patch that adds the null skb check before assignment.

How to confirm the fix worked

Verify kernel source contains the added conditional skb null check and warning logic in the ibmvnic transmit code path; confirm no skb leaks occur under high transmit load after update.

Typical attack path

1. Identify systems running vulnerable ibmvnic driver
2. Induce transmit path conditions that desynchronize internal maps
3. Sustain operations to accumulate skb leaks
4. Observe resulting TCP congestion and ETIMEDOUT failures

How to detect it

Search kernel logs for ibmvnic warnings about non-null skb addresses during transmit; inspect for unexplained memory growth tied to the driver under network load.

What your security team should do

• Prioritize kernel update on all systems using ibmvnic
• Enable driver debug logging to catch desync warnings
• Monitor network timeout rates as a proxy for exposure