CVE-2026-80802 Linux CVE debrief

Who should care

Linux kernel developers and administrators who use the NFC FDP driver should review and apply the patch to fix the vulnerability. Additionally, security teams should monitor for suspicious activity on the NFC FDP driver.

Why it matters

The Linux kernel's NFC FDP driver vulnerability can lead to potential code execution, data packet leaks, and increased risk of privilege escalation. Linux kernel developers and administrators should review and apply the patch to fix the vulnerability.

• Potential code execution on affected systems
• Data packet leak due to skb allocation issue
• Increased risk of privilege escalation
• Need for patch review and application

Technical summary

The Linux kernel's NFC FDP driver does not validate the device-reported read length, allowing a malicious device to send a specially crafted packet that can overwrite the stack canary and return address, potentially leading to code execution. Additionally, the driver allocates one data skb per iteration and assumes a length packet followed by a data packet, which can cause a leak of the first skb when the second allocation overwrites it.

Defensive priority

High

Recommended defensive actions

• Review and apply the Linux kernel patch to fix the vulnerability
• Restrict access to the NFC FDP driver to only trusted devices
• Monitor for suspicious activity on the NFC FDP driver
• 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 is described in the Linux kernel patch notes and is referenced by multiple source references. The Linux kernel's NFC FDP driver does not validate the device-reported read length, allowing a malicious device to send a specially crafted packet that can overwrite the stack canary and return address, potentially leading to code execution. Additionally, the driver allocates one data skb per iteration and assumes a length packet followed by a data packet, which can cause a leak of the first skb when the second allocation

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.