CVE-2026-31629CWE-667

CVE-2026-31629

High · published April 24, 2026

CVSS v3.1
8.8
EPSS
0%
Percentile
28.7
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
8.8 · HIGH
Vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.00361 · 28.7th percentile
Weakness
CWE-667 · Improper Locking
Published
2026-04-24T19:16Z
Affected products (5)
ProductVersionsFixed in
linux/linux_kernel≥ 3.3, < 6.6.1366.6.136
linux/linux_kernel≥ 6.7, < 6.12.836.12.83
linux/linux_kernel≥ 6.13, < 6.18.246.18.24
linux/linux_kernel≥ 6.19, < 6.19.146.19.14
linux/linux_kernel≥ 7.0, < 7.0.17.0.1
References (10)
EPSS history
Timeline
  • 24 APR 14:42Z
    nfc: llcp: add missing return after LLCP_CLOSED checks
    cvelistv5