Out-of-bounds reads via unbounded service-name logging
Published Oct 18, 2026 · Updated Oct 18, 2026
Out-of-bounds reads in Linux NFC LLCP allow local users to cause reads past service-name buffers through crafted debug-log strings. The nfc_llcp_wks_sap() and nfc_llcp_build_sdreq_tlv() functions pass buffers without guaranteed null termination to pr_debug() with %s, ignoring their explicit lengths. The affected debug callsites must execute with logging enabled; the reported invalid read does not establish arbitrary memory retrieval or code execution.
Summary
What happened
Out-of-bounds reads in Linux NFC LLCP allow local users to cause reads past service-name buffers through crafted debug-log strings. The nfc_llcp_wks_sap() and nfc_llcp_build_sdreq_tlv() functions pass buffers without guaranteed null termination to pr_debug() with %s, ignoring their explicit lengths. The affected debug callsites must execute with logging enabled; the reported invalid read does not establish arbitrary memory retrieval or code execution.
The record
- CVE
- CVE-2026-98576
- 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.10
- Affected versionversion=d9b8d8e19b073096d3609bbd60f82148d128b555 <4262b12277a3e056c95fc49e9c4d7bd97035d16c
- Affected versionversion=d9b8d8e19b073096d3609bbd60f82148d128b555 <6d4ca872830e46fcca9c086bf19fa9bd2faf09d2
- Affected versionversion=d9b8d8e19b073096d3609bbd60f82148d128b555 <75bfd9ef4da2fb49dac1f19880d2ac4ccd07b45b
- Affected versionversion=d9b8d8e19b073096d3609bbd60f82148d128b555 <75f7c5a42fa1483f5912279a749417c284ad708f
- Affected versionversion=d9b8d8e19b073096d3609bbd60f82148d128b555 <7dcf371a35632f035baf77bcf2c129165f772ce4
- Affected versionversion=d9b8d8e19b073096d3609bbd60f82148d128b555 <8978dff632519712d1fa432991e1f2e857f90239
- Affected versionversion=d9b8d8e19b073096d3609bbd60f82148d128b555 <8afb6c194f5781798d3ab3edf243cf5a24a9d1f9
- Affected versionversion=d9b8d8e19b073096d3609bbd60f82148d128b555 <a143f7835faa4fe0178448289feea4f84eeee8d6
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
- Syzkaller local NFC LLCP reproducerproof of concept · demonstrated
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