CVE-2026-98050 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, Linux distribution maintainers, and users of Linux-based systems, particularly those using the mlxsw spectrum_ptp component, should assess exposure and apply patches or mitigations as needed.

Why it matters

This vulnerability in the Linux kernel's mlxsw spectrum_ptp component could lead to a kernel panic and potentially allow for denial of service or code execution. Linux kernel developers and maintainers, Linux distribution maintainers, and users of Linux-based systems should assess exposure and apply patches or mitigations as needed.

• Denial of service due to kernel panic
• Potential code execution or privilege escalation
• List corruption and system instability
• Verification of patch application and system hardening

Technical summary

The vulnerability is caused by a call to napi_gro_receive() from a GC workqueue context, which can lead to list corruption and potentially allow for denial of service or code execution. The fix involves adding an ingress-delivery helper for the PTP packet_finish() path that calls netif_receive_skb() instead of napi_gro_receive(). This change ensures that the PTP packets are handled properly and prevents the list corruption that can occur when napi_gro_receive() is called from a GC workqueue context. The affected product context is the Linux kernel's mlxsw spectrum_ptp component, and the defensive impact is the prevention of potential denial of service or code execution attacks.

Defensive priority

High

Recommended defensive actions

• Review and apply the provided Linux kernel patches to fix the vulnerability
• Monitor system logs for potential denial of service or code execution attempts
• Consider implementing additional security measures to protect against potential exploits
• 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 CVE record and NVD detail page provide information on the vulnerability, including its CVSS score and vector. The Linux kernel patch notes and Git commit hashes provide technical details on the vulnerability and its fix.

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.