CVE-2025-38122

What it actually does

Missing NULL check after gve_alloc_pending_packet() in gve_tx_add_skb_dqo allows dereference of a NULL pointer during TX path in the gve driver under allocation failure.

Why it matters to the business

Low-memory conditions on systems using the affected Linux kernel driver can trigger kernel crashes or instability, disrupting network connectivity in virtualized or containerized environments; the issue has been present for over a year with minimal observed exploitation risk but appears in multiple downstream packages.

How an attack unfolds

An attacker triggers repeated TX operations while inducing memory pressure to force gve_alloc_pending_packet() to return NULL, causing the unchecked pointer dereference; listed threat actors associated with Linux kernel privilege escalation campaigns could chain this memory corruption into code execution or denial of service.

How to fix it

Update to fixed kernel commit ae98a1787fdcb0096d122bc80d93c3c7d812c04b or later; for AlmaLinux 9 packages upgrade skopeo and skopeo-tests to 2:1.18.1-2.el9_6 or newer.

How to confirm the fix worked

Confirm presence of the NULL check in gve_tx_add_skb_dqo after gve_alloc_pending_packet(); verify package versions match the listed fixed releases and test TX operations under memory pressure.

Typical attack path

1. Gain local execution or container access on an affected kernel
2. Induce memory pressure via allocation-heavy workloads
3. Trigger gve TX path through network activity
4. Force allocation failure in gve_alloc_pending_packet()
5. Dereference the NULL pointer to crash or corrupt kernel state

How to detect it

Review kernel logs for gve driver oops or NULL dereference messages during TX activity; correlate with memory pressure events and any privilege escalation attempts noted by the listed threat actors.

What your security team should do

• Prioritize kernel and skopeo package upgrades on all affected systems within standard maintenance windows
• Monitor EPSS trend and any new threat actor activity tied to Linux kernel memory corruption
• Harden low-memory scenarios with resource limits for containers and virtual machines