CVE-2024-50145

What it actually does

Null pointer dereference in the octeon_ep Linux kernel driver when build_skb() returns NULL during RX queue processing in __octep_oq_process_rx(), allowing continued polling without immediate NAPI break and skipping packet handling with an added alloc_failures statistic.

Why it matters to the business

Potential kernel instability or crashes during network receive operations on systems using the affected driver, increasing operational risk and requiring urgent patching especially given high ecosystem prevalence of Linux kernel components.

How an attack unfolds

An attacker triggers memory pressure or allocation failures during NAPI polling in the octeon_ep RX path, causing build_skb() to return NULL; the unhandled case leads to dereference and potential crash, with threat actors in 2024 zero-day campaigns and Linux kernel-related exploits potentially leveraging similar patterns for denial of service.

How to fix it

Update to fixed kernel versions addressing the allocation failure handling in __octep_oq_process_rx(); apply the resolution that adds NULL checks, fragment unmapping helper, and alloc_failures counter increment.

How to confirm the fix worked

Confirm kernel version includes the skb allocation failure handling patch; inspect driver statistics for alloc_failures counter and verify absence of NULL dereference paths in __octep_oq_process_rx() via code review or testing under memory pressure.

Typical attack path

1. Identify systems running vulnerable Linux kernel with octeon_ep driver enabled
2. Induce memory allocation pressure on the target during network RX activity
3. Trigger build_skb() failure inside __octep_oq_process_rx() called from NAPI poll
4. Cause NULL dereference leading to kernel panic or driver malfunction

How to detect it

Review kernel logs for NULL pointer dereference oops in octeon_ep or __octep_oq_process_rx(); search NAPI polling traces and driver statistics for spikes in alloc_failures; correlate with threat actor activity in Linux kernel exploitation campaigns.

• octeon_ep
• __octep_oq_process_rx
• build_skb
• alloc_failures

What your security team should do

• Prioritize kernel upgrades on all systems exposing octeon_ep interfaces due to 704 days since publication
• Monitor EPSS trend stability and absence from KEV for risk assessment
• Enable driver statistics collection to track allocation failures post-deployment