In the Linux kernel's NFC LLCP implementation, two functions incorrectly fall through after handling a closed socket state. The code calls release_sock() and nfc_llcp_sock_put() twice, causing a reference count underflow and a use‑after‑free. This memory corruption can allow an attacker to execute arbitrary code or crash the system if the double release is triggered during normal operation.

The vulnerability affects all Linux kernel builds that include the buggy nfc_llcp_recv_hdlc() and nfc_llcp_recv_disc() functions. Any distribution that has not applied the patch commit adding the missing return statements remains vulnerable. The issue is present in the mainline kernel source before the upstream fix.

The CVSS score of 8.8 indicates high severity, but the EPSS score of less than 1% shows a low probability of real‑world exploitation. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. Based on the code path, the attack likely requires local or privileged access to trigger the double release; remote exploitation would need a vector that can manipulate NFC LLCP traffic against the target kernel.