Memory disclosure via unchecked HID report offsets
Published Oct 18, 2026 · Updated Oct 18, 2026
An out-of-bounds read in the Linux Wacom HID driver allows attackers to read kernel memory via a crafted HID descriptor and report. The wacom_wac_pen_serial_enforce() function uses the descriptor's usage count rather than its report slot count to calculate extraction offsets, reading beyond the received buffer. Exposure requires attacker-controlled HID input to reach this driver path; extracted bytes reach userspace through MSC_SERIAL input events.
Summary
What happened
An out-of-bounds read in the Linux Wacom HID driver allows attackers to read kernel memory via a crafted HID descriptor and report. The wacom_wac_pen_serial_enforce() function uses the descriptor's usage count rather than its report slot count to calculate extraction offsets, reading beyond the received buffer. Exposure requires attacker-controlled HID input to reach this driver path; extracted bytes reach userspace through MSC_SERIAL input events.
The record
- CVE
- CVE-2026-98499
- Published
- Oct 18, 2026
- Updated
- Oct 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- 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=4.16
- Affected versionversion=83417206427bdf0fef9fa69957807194f25923c3 <26471d954bbfbfb9032994f7f485802ee20e0582
- Affected versionversion=83417206427bdf0fef9fa69957807194f25923c3 <456afe4707e23cc114ad833197f63b52bb8fd1e7
- Affected versionversion=83417206427bdf0fef9fa69957807194f25923c3 <4b09b7c84b8633cd041181616bd15bf5e73c164d
- Affected versionversion=83417206427bdf0fef9fa69957807194f25923c3 <65e7c4b5366b770c60dfefac3f1d06e33a9e411e
- Affected versionversion=83417206427bdf0fef9fa69957807194f25923c3 <9aa237cf66495b2426ddde8532e9b08a0ed83aaa
- Affected versionversion=83417206427bdf0fef9fa69957807194f25923c3 <9aa62f967b6a4bb30aa3b778e02c8a5ca6bcde51
- Affected versionversion=83417206427bdf0fef9fa69957807194f25923c3 <c3129e6f26e18c0886ede7265f187a7ec289e1d1
- Affected versionversion=83417206427bdf0fef9fa69957807194f25923c3 <eaa7d29341ef4b91e84ad097562982288a7c376c
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