CVE-2026-99079 Linux CVE debrief

Who should care

Linux system administrators, security teams, and developers working with AF_XDP sockets and XDP redirects should assess exposure and prioritize remediation. Linux system administrators and security teams should prioritize verifying exposure and applying remediation, focusing on systems utilizing AF_XDP sockets and XDP redirects. Operators managing Linux systems with AF_XDP sockets and XDP redirects should review and apply patches from Linux vendors for the

Why it matters

This vulnerability in the Linux kernel's net/mlx5e component can lead to silent failures and potential data corruption, requiring verification and remediation priority for Linux systems utilizing AF_XDP sockets and XDP redirects.

• Potential double-publish of the same UMEM frame.
• Silent failure without kernel warning or splat.
• Possible data corruption or unexpected behavior.
• Verification priority for Linux systems utilizing AF_XDP sockets and XDP redirects.

Technical summary

The vulnerability occurs in the Linux kernel's net/mlx5e component, specifically in the handling of XSK buffers during refill retries. When an XDP redirect to an AF_XDP socket fails due to a full RX ring, the XSK core frees the buffer. However, the driver releases the WQE's XSK buffer before allocating a replacement, potentially leading to a double-publish of the same UMEM frame. This issue arises when an XDP redirect to an AF_XDP socket fails due to a full RX ring, and the XSK core frees the buffer. During a subsequent batched refill of a legacy cyclic RQ, the driver releases the WQE's XSK buffer before allocating a replacement. If the refill only partially succeeds, a WQE without a replacement retains its old

Defensive priority

Linux system administrators and security teams should prioritize verifying exposure and applying remediation, focusing on systems utilizing AF_XDP sockets and XDP redirects.

Recommended defensive actions

• Verify Linux kernel versions and assess exposure based on the provided affected versions.
• Review and apply patches from Linux vendors for the affected component.
• Monitor system logs for events related to XDP redirects and AF_XDP sockets.
• Implement compensating controls, such as rate limiting or monitoring XDP redirect traffic.
• 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.

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, affected versions, and references to source code changes. However, the corpus does not establish versions, exploitation, impact, or remediation beyond vendor-provided information.

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.