CVE-2026-98580

published 18 Oct 2026 · updated 20 Nov 2026

nfc: llcp: Fix race condition in accept_queue lifecycle

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel da8a07757383614a8380a0f7dd54749d2687b82e, Kernel 41256821762a7114906b178826d17098e2fa5992, Kernel 53867f6acb1af7f12d6485fa8a2819318f89083b and 12 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=50b78b2a6500d0e97c204c1b6c51df8c17358bbe <da8a07757383614a8380a0f7dd54749d2687b82e, >=50b78b2a6500d0e97c204c1b6c51df8c17358bbe <41256821762a7114906b178826d17098e2fa5992, >=50b78b2a6500d0e97c204c1b6c51df8c17358bbe <53867f6acb1af7f12d6485fa8a2819318f89083b, >=50b78b2a6500d0e97c204c1b6c51df8c17358bbe <54adcabb0f1deef1bdae5fc64779ed6d442721c9, >=50b78b2a6500d0e97c204c1b6c51df8c17358bbe <7c938aad5108382c6ad7453c4b5ee8ae3f3252ed, >=50b78b2a6500d0e97c204c1b6c51df8c17358bbe <c3eef2f988a3db9690369d7cef9a3344dd9788d3, >=50b78b2a6500d0e97c204c1b6c51df8c17358bbe <d2093a0981138876212bc5f473bdbfba0786e064, >=50b78b2a6500d0e97c204c1b6c51df8c17358bbe <d5e1c92d09caed19f2988739695ce611a86ba6f8, =3.7da8a07757383614a8380a0f7dd54749d2687b82e, 41256821762a7114906b178826d17098e2fa5992, 53867f6acb1af7f12d6485fa8a2819318f89083b, 54adcabb0f1deef1bdae5fc64779ed6d442721c9, 7c938aad5108382c6ad7453c4b5ee8ae3f3252ed, c3eef2f988a3db9690369d7cef9a3344dd9788d3, d2093a0981138876212bc5f473bdbfba0786e064, d5e1c92d09caed19f2988739695ce611a86ba6f8
linux-kernel: Kernel>=5.11.0 <5.15.222, >=5.16.0 <6.1.189, >=6.13.0 <6.18.55, >=6.19.0 <7.2.9, >=6.2.0 <6.6.158, >=6.7.0 <6.12.112, >=3.7.0 <5.10.2715.15.222, 6.1.189, 6.18.55, 7.2.9, 6.6.158, 6.12.112, 5.10.271

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-98580 severity on Zeptric[![CVE-2026-98580](https://zeptric.io/badge/cve/CVE-2026-98580.svg)](https://zeptric.io/cve/CVE-2026-98580)