Service-address hijacking via prefix-only service-name matching
Published Oct 18, 2026 · Updated Oct 18, 2026
Service-name matching in Linux NFC LLCP allows local users to hijack well-known service addresses through socket binding. In net/nfc/llcp_core.c, nfc_llcp_wks_sap() compares only the supplied name length, accepting a shortened prefix as a complete well-known service name. Exploitation requires access to an NFC device and the ability to bind an LLCP socket; the disclosed consequence is service-address misassignment, not demonstrated kernel code execution.
Summary
What happened
Service-name matching in Linux NFC LLCP allows local users to hijack well-known service addresses through socket binding. In net/nfc/llcp_core.c, nfc_llcp_wks_sap() compares only the supplied name length, accepting a shortened prefix as a complete well-known service name. Exploitation requires access to an NFC device and the ability to bind an LLCP socket; the disclosed consequence is service-address misassignment, not demonstrated kernel code execution.
The record
- CVE
- CVE-2026-98577
- Published
- Oct 18, 2026
- Updated
- Oct 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- 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.3
- Affected versionversion=d646960f7986fefb460a2b062d5ccc8ccfeacc3a <0a0412745c86acd089c6460da715ab966b1615e7
- Affected versionversion=d646960f7986fefb460a2b062d5ccc8ccfeacc3a <0c83a8a45fed256ccc5fe7160b436b671fc79fb8
- Affected versionversion=d646960f7986fefb460a2b062d5ccc8ccfeacc3a <32b5f0b338bf59391a1cff9a6190a72c4d2c1ba8
- Affected versionversion=d646960f7986fefb460a2b062d5ccc8ccfeacc3a <408cff6bd60636df201274d320edfdfde9ed41db
- Affected versionversion=d646960f7986fefb460a2b062d5ccc8ccfeacc3a <6fad2c34d451d11a9f3f946cae1105fee91d96b8
- Affected versionversion=d646960f7986fefb460a2b062d5ccc8ccfeacc3a <aa555ed5ed0d15efbaf27e0e9f152a6df715278a
- Affected versionversion=d646960f7986fefb460a2b062d5ccc8ccfeacc3a <bf41af8f910cbb5d776a1dfa0671d31a7e262e28
- Affected versionversion=d646960f7986fefb460a2b062d5ccc8ccfeacc3a <f234197f3bda3aea5d4b1e591d6bcb3660a8b3fc
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
No sourced classifications are available.
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