CVE-2026-98580: Linux kernel · nfc: llcp: Fix race condition in accept_queue lifecycle
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in da8a07757383614a8380a0f7dd54749d2687b82e : patch Linux kernel soon.
Data as of 26 Oct 2026, 12:55 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in da8a07757383614a8380a0f7dd54749d2687b82e, d2093a0981138876212bc5f473bdbfba0786e064, d5e1c92d09caed19f2988739695ce611a86ba6f8 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available and has been applied in the Linux kernel. Users should update to a kernel version that includes the referenced fixes. No additional mitigation actions are required beyond applying the official patch.
Description
A race condition vulnerability in the Linux kernel's NFC LLCP socket handling was fixed. The flaw involved concurrent unlinking and releasing of the same child socket due to improper synchronization between socket release and accept dequeue operations. This could lead to use-after-free or NULL pointer dereference errors. The fix involves changing locking mechanisms, deferring resource release to a workqueue, and adding checks to prevent hangs and ensure idempotency.
References
- git.kernel.org/stable/c/54adcabb0f1deef1bdae5fc64779ed6d442721c9 (opens in a new tab)
- git.kernel.org/stable/c/7c938aad5108382c6ad7453c4b5ee8ae3f3252ed (opens in a new tab)
- git.kernel.org/stable/c/d2093a0981138876212bc5f473bdbfba0786e064 (opens in a new tab)
- git.kernel.org/stable/c/41256821762a7114906b178826d17098e2fa5992 (opens in a new tab)
- git.kernel.org/stable/c/53867f6acb1af7f12d6485fa8a2819318f89083b (opens in a new tab)
- git.kernel.org/stable/c/da8a07757383614a8380a0f7dd54749d2687b82e (opens in a new tab)
- git.kernel.org/stable/c/d5e1c92d09caed19f2988739695ce611a86ba6f8 (opens in a new tab)
- git.kernel.org/stable/c/c3eef2f988a3db9690369d7cef9a3344dd9788d3 (opens in a new tab)