CVE-2022-49019

What it actually does

NULL pointer dereference in nixge_hw_dma_bd_release() when priv->rx_bd_v allocation fails during nixge_hw_dma_bd_init() in the Linux kernel nixge Ethernet driver.

Why it matters to the business

Potential kernel panic or denial of service on systems using the affected network driver, leading to system instability and unplanned downtime; low exploitation likelihood reduces urgency but kernel-level issues affect availability broadly.

How an attack unfolds

An attacker triggers resource exhaustion to cause rx_bd_v allocation failure during driver initialization, then induces a code path that calls nixge_hw_dma_bd_release() without validity checks, resulting in a NULL dereference crash.

How to fix it

Upgrade Linux kernel to a version containing commit 910c0264b64ef2dad8887714a7c56c93e39a0ed3 or later stable releases that move the dereference loop under a validity check for rx_bd_v.

How to confirm the fix worked

Verify kernel source includes the fix commit or check running kernel version against affected git trees; test driver initialization under low-memory conditions to confirm no crash.

Typical attack path

1. Identify systems running vulnerable nixge driver in Linux kernel
2. Exhaust memory or other resources to force allocation failure in nixge_hw_dma_bd_init()
3. Trigger driver teardown or error path invoking nixge_hw_dma_bd_release()
4. Cause kernel panic via NULL pointer dereference

How to detect it

Review kernel logs for nixge-related NULL dereference oops or panics; examine dmesg output around driver load/unload events for allocation failure indicators.

What your security team should do

• Prioritize kernel updates on any systems using nixge Ethernet hardware
• Monitor for kernel oops or panic logs related to nixge driver
• Apply the fix from stable kernel trees as no KEV or high EPSS indicates immediate widespread threat