CVE-2026-98580
Received Received - Intake

Race Condition in Linux Kernel NFC LLCP Socket Handling

Vulnerability report for CVE-2026-98580, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-18

Last updated on: 2026-10-18

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: Fix race condition in accept_queue lifecycle In nfc_llcp_socket_release(), sockets and listener accept queues are walked under the local sockets rwlock and bh_lock_sock(). However, bh_lock_sock() does not synchronise against process-context lock_sock() held by nfc_llcp_accept_dequeue() during accept(). Because socket_release() does not check sock_owned_by_user(), both paths can concurrently unlink and release the same child socket, resulting in use-after-free or a NULL pointer dereference of child->parent in nfc_llcp_accept_unlink(). Fix this synchronisation race by having nfc_llcp_socket_release() use process-context lock_sock() instead of bh_lock_sock(): 1. Pop sockets from the local sockets list under the write lock using nfc_llcp_sock_list_pop() so lock_sock() can be acquired without holding the rwlock. 2. Because lock_sock() can sleep, defer the final release of the nfc_llcp_local structure to a workqueue (release_work). This avoids a sleeping-in-atomic bug when the last local reference is dropped from softirq context. Additionally, hold a single device reference on local from registration until final destruction. 3. In nfc_llcp_local_get(), use kref_get_unless_zero() to prevent resurrecting a local object whose teardown has been scheduled. 4. In llcp_sock_accept(), verify that the listener socket state is still LLCP_LISTEN after waking from schedule_timeout() to prevent hangs if the listener is closed concurrently. 5. When unlinking unaccepted child sockets during listener release, unlink them from local->sockets, call sock_orphan(), and drop their initial sk_alloc creation reference via sock_put(). 6. Make nfc_llcp_accept_unlink() idempotent by guarding parent access with a NULL check.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-18
Last Modified
2026-10-18
Generated
2026-10-18
AI Q&A
2026-10-18
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 9 associated CPEs
Vendor Product Version / Range
Linux Linux 50b78b2a6500d0e97c204c1b6c51df8c17358bbe
Linux Linux 50b78b2a6500d0e97c204c1b6c51df8c17358bbe
Linux Linux 50b78b2a6500d0e97c204c1b6c51df8c17358bbe
Linux Linux 50b78b2a6500d0e97c204c1b6c51df8c17358bbe
Linux Linux 50b78b2a6500d0e97c204c1b6c51df8c17358bbe
Linux Linux 50b78b2a6500d0e97c204c1b6c51df8c17358bbe
Linux Linux 50b78b2a6500d0e97c204c1b6c51df8c17358bbe
Linux Linux 50b78b2a6500d0e97c204c1b6c51df8c17358bbe
Linux Linux 3.7

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a race condition in the Linux kernel's NFC LLCP (Near Field Communication Logical Link Control Protocol) module. It occurs when sockets and listener accept queues are accessed concurrently without proper synchronization. Specifically, the issue arises when nfc_llcp_socket_release() and nfc_llcp_accept_dequeue() operate on the same child socket simultaneously, leading to use-after-free or NULL pointer dereference errors.

Detection Guidance

This vulnerability is specific to the Linux kernel's NFC LLCP (Near Field Communication Logical Link Control Protocol) implementation. Detection requires checking if your system is running a vulnerable kernel version. Use commands like 'uname -a' to check the kernel version and compare it against patched versions. Monitor kernel logs for crashes or errors related to NFC or socket operations.

Impact Analysis

This vulnerability could allow an attacker to cause system crashes or execute arbitrary code with kernel privileges by exploiting the race condition. It primarily affects systems using NFC functionality, potentially leading to denial-of-service or privilege escalation attacks.

Mitigation Strategies

Apply the latest kernel updates provided by your Linux distribution to patch this vulnerability. If immediate patching is not possible, consider disabling the NFC LLCP module by unloading the 'llcp' kernel module using 'modprobe -r llcp'. Ensure no critical services depend on NFC LLCP before disabling.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-98580. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart