Memory exhaustion via LLCP socket-list race
Published Oct 18, 2026 · Updated Oct 18, 2026
Race condition in Linux NFC LLCP allows local users to exhaust kernel memory through peer-supplied disconnect messages. In nfc_llcp_recv_dm(), DM(NOBOUND)/DM(REJ) closes connecting sockets without locking or unlinking them, causing release to modify their list under the wrong lock and leak socket references. Exploitation requires unprivileged local LLCP sockets, concurrent connection activity, and an established NFC LLCP peer; the documented consequence is memory-exhaustion denial of service, without a specified crash or reboot.
Summary
What happened
Race condition in Linux NFC LLCP allows local users to exhaust kernel memory through peer-supplied disconnect messages. In nfc_llcp_recv_dm(), DM(NOBOUND)/DM(REJ) closes connecting sockets without locking or unlinking them, causing release to modify their list under the wrong lock and leak socket references. Exploitation requires unprivileged local LLCP sockets, concurrent connection activity, and an established NFC LLCP peer; the documented consequence is memory-exhaustion denial of service, without a specified crash or reboot.
The record
- CVE
- CVE-2026-98581
- Published
- Oct 18, 2026
- Updated
- Oct 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.001
- Attack vector
- local
- Privileges
- authenticated
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.6
- Affected versionversion=a69f32af86e389dd232b1bb2269e202c1bfcc60f <320a2ff49bdce3f9a437b9a9ff341ff27d3bdbf1
- Affected versionversion=a69f32af86e389dd232b1bb2269e202c1bfcc60f <7fb2c0eeb79bfad64065f539a453138abd0edda6
- Affected versionversion=a69f32af86e389dd232b1bb2269e202c1bfcc60f <812731dd8511f5768f4ff279b3c18d85cd21da4b
- Affected versionversion=a69f32af86e389dd232b1bb2269e202c1bfcc60f <b94cf09720543cc34256c7aa88f8059cbe7c0419
- Affected versionversion=a69f32af86e389dd232b1bb2269e202c1bfcc60f <bf1460acdf8cf5a07c819f59785d40f20d113099
- Affected versionversion=a69f32af86e389dd232b1bb2269e202c1bfcc60f <c1e9ed52a6697354366dddf190fbacee8ed2f7c5
- Affected versionversion=a69f32af86e389dd232b1bb2269e202c1bfcc60f <dba1d9c7134afcb4b1bfad8c1b1b3f0ab5189b08
- Affected versionversion=a69f32af86e389dd232b1bb2269e202c1bfcc60f <dd2d24add86b3b63cd87cf2feff98ae119ba19a6
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