Signal is active with 2 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: add missing return after LLCP_CLOSED checks In nfc_llcp_recv_hdlc() and nfc_llcp_recv_disc(), when the socket state is LLCP_CLOSED, the code correctly calls release_sock() and nfc_llcp_sock_put() but fails to return. Execution falls through to the remainder of the function, which calls release_sock() and nfc_llcp_sock_put() again. This results in a double release_sock() and a refcount underflow via double nfc_llcp_sock_put(), leading to a use-after-free. Add the missing return statements after the LLCP_CLOSED branches in both functions to prevent the fall-through.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
AVAILABLE
Momentum
NONE
If you run products in this scope, you should treat this CVE as relevant to your environment.
CVE-2026-31629 Missing Return Statement Causing Use-After-Free in Linux Kernel NFC LLCP https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-31629
Post summary
The text provides a basic announcement of CVE-2026-31629, naming it as a use‑after‑free flaw in the Linux Kernel NFC LLCP, but lacks any additional details regarding PoC, exploitation, or mitigation.
CVE-2026-31629 In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: add missing return after LLCP_CLOSED checks In nfc_llcp_recv_hdlc() and nfc_llcp_recv… https://www.cve.org/CVERecord?id=CVE-2026-31629
Post summary
The text announces that CVE‑2026‑31629 has been fixed in the Linux kernel; no PoC, exploit, or active exploitation details are provided.
1 of 1 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| OS | linux | linux_kernel | - | - | - |