Kernel crash via LLCP socket-lifecycle race
Published Oct 18, 2026 · Updated Oct 18, 2026
A race in Linux NFC LLCP socket handling allows attackers to crash the kernel via concurrent accept() and socket teardown. In nfc_llcp_socket_release(), bh_lock_sock() does not exclude the process-context lock held during acceptance, allowing both paths to unlink and release the same child socket. Triggering requires overlapping acceptance and teardown of queued NFC LLCP child sockets, resulting in use-after-free or a NULL pointer dereference; privilege escalation is not established.
Summary
What happened
A race in Linux NFC LLCP socket handling allows attackers to crash the kernel via concurrent accept() and socket teardown. In nfc_llcp_socket_release(), bh_lock_sock() does not exclude the process-context lock held during acceptance, allowing both paths to unlink and release the same child socket. Triggering requires overlapping acceptance and teardown of queued NFC LLCP child sockets, resulting in use-after-free or a NULL pointer dereference; privilege escalation is not established.
The record
- CVE
- CVE-2026-98580
- Published
- Oct 18, 2026
- Updated
- Oct 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 18, 2026CVE publishedPublication date reported by the CVE source.
- Oct 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.7
- Affected versionversion=50b78b2a6500d0e97c204c1b6c51df8c17358bbe <41256821762a7114906b178826d17098e2fa5992
- Affected versionversion=50b78b2a6500d0e97c204c1b6c51df8c17358bbe <53867f6acb1af7f12d6485fa8a2819318f89083b
- Affected versionversion=50b78b2a6500d0e97c204c1b6c51df8c17358bbe <54adcabb0f1deef1bdae5fc64779ed6d442721c9
- Affected versionversion=50b78b2a6500d0e97c204c1b6c51df8c17358bbe <7c938aad5108382c6ad7453c4b5ee8ae3f3252ed
- Affected versionversion=50b78b2a6500d0e97c204c1b6c51df8c17358bbe <c3eef2f988a3db9690369d7cef9a3344dd9788d3
- Affected versionversion=50b78b2a6500d0e97c204c1b6c51df8c17358bbe <d2093a0981138876212bc5f473bdbfba0786e064
- Affected versionversion=50b78b2a6500d0e97c204c1b6c51df8c17358bbe <d5e1c92d09caed19f2988739695ce611a86ba6f8
- Affected versionversion=50b78b2a6500d0e97c204c1b6c51df8c17358bbe <da8a07757383614a8380a0f7dd54749d2687b82e
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started