CVE-2026-90059 Linux CVE debrief

Who should care

Defenders responsible for Linux kernel-based systems, especially those using ARM32 architectures, should assess exposure and prioritize patching or mitigation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to ensure the stability and security of their systems.

Why it matters

A vulnerability in the Linux kernel's stmmac network driver can cause a kernel panic on certain architectures when receiving an ICMP echo request due to IP header misalignment.

• Potential kernel panic and system crash on ARM32 architectures
• Disruption of network services and applications
• Increased risk of denial-of-service (DoS) attacks
• Need for patching or mitigation to prevent exploitation

Technical summary

The Linux kernel's stmmac network driver has a vulnerability that can cause a kernel panic on certain architectures when receiving an ICMP echo request. The issue arises from the RX DMA offset not accounting for NET_IP_ALIGN after the conversion to zero-copy RX path. This misalignment can lead to an unhandled fault and subsequently a fatal exception in interrupt. The patch restores NET_IP_ALIGN in the RX DMA offset, which should prevent the kernel panic caused by IP header misalignment. Defenders should prioritize patching or mitigating this vulnerability, especially on ARM32 architectures where it can cause a kernel panic.

Defensive priority

Defenders should prioritize patching or mitigating this vulnerability, especially on ARM32 architectures where it can cause a kernel panic.

Recommended defensive actions

• Apply the official patch to restore NET_IP_ALIGN in the RX DMA offset
• Assess exposure and prioritize patching for ARM32 architectures
• Monitor for ICMP echo requests and kernel panics
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability was introduced by a change in the RX path of the stmmac driver, which was converted to use zero-copy. However, the NET_IP_ALIGN was not carried over, leading to IP header misalignment on certain architectures. Defenders should verify the patch status of Linux kernel-based systems, especially those using ARM32 architectures, and assess exposure to prioritize patching or mitigation. The patch restores NET_IP_ALIGN in the RX DMA offset, which should prevent the kernel panic caused by IP header misalignment.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.