Linux Kernel NFC LLCP Socket State Handling Vulnerability Leading to Use-After-Free

Vulnerability

A use-after-free vulnerability has been identified in the Linux kernel's NFC LLCP (Logical Link Control Protocol) implementation. This issue arises in the functions 'nfc_llcp_recv_hdlc()' and 'nfc_llcp_recv_disc()'. When the socket state is 'LLCP_CLOSED', the code correctly releases the socket but fails to return, causing execution to fall through. This oversight leads to a double release of the socket, creating a reference count underflow and a use-after-free condition. The vulnerability affects the Linux kernel stable tree.

Impact

The vulnerability causes a use-after-free condition, which can lead to memory corruption and potentially allow for arbitrary code execution.

Reproduction

The vulnerability can be reproduced by invoking the NFC LLCP reception functions 'nfc_llcp_recv_hdlc()' or 'nfc_llcp_recv_disc()' with the socket state set to 'LLCP_CLOSED'. This will trigger the double release of the socket, causing the use-after-free condition.

Remediation

The vulnerability has been addressed by adding the missing return statements after the 'LLCP_CLOSED' checks in both affected functions. Users can apply the latest patches available in the Linux kernel stable tree to mitigate this vulnerability.

Added: Apr 24, 2026, 5:01 PM
Updated: Apr 24, 2026, 5:01 PM

Vulnerability Rating

Custom Algorithm
spread
9.0
impact
2.5
exploitability
5.3
remediation
7.7
relevance
6.6
threat
4.8
urgency
2.9
incentive
0.0

Our algorithm analyzes dozens of metrics to generate these 8 key vulnerability categories, which are then combined to calculate the overall risk score.