Live › vulnerability › CVE-2026-98499
Go to dashboardA malicious or malformed USB HID device with a crafted descriptor can make the Wacom driver read memory beyond the end of a received report. The leaked value is reported to userspace as an MSC_SERIAL input event, so an attacker gets kernel memory contents as information disclosure.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems running a Linux kernel with the Wacom HID driver that can receive reports from a Wacom-style pen tablet, including devices an attacker can plug in or emulate through UHID. Machines without Wacom tablets or with the module not loaded are less exposed. The sources do not say which kernel versions are fixed beyond the v6.12.105 reproduction.
No product ranges from the sources yet.
uname -r and compare against the fixed kernel version in your distribution's advisory (unknown in the sources)lsmod | grep wacommodprobe -r wacom if no Wacom tablet is in useEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
In the Linux kernel, the following vulnerability has been resolved:
HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce()
The 'wacom_wac_pen_serial_enforce()' function may calculate and pass an invalid offset to hid_field_extract(), resulting in memory reads at incorrect addresses -- possibly beyond the end of the report. If a field in the HID descriptor lists more usages than its Report Count actually reserves space for, the function's inner 'j' will walk past the end of the field:
for (i = 0; i < report->maxfield; i++) {
for (j = 0; j < report->field[i]->maxusage; j++) {
...
value = hid_field_extract(hdev, raw_data + 1,
offset + j * size, size);
A descriptor listing 12288 usages against Report Count 1 has the loop extract the usage at index 12287 from bit offset 98296 -- about 12 KB past a 2-byte received report. The value is stored in wacom_wac->serial[0] and can reach userspace as an MSC_SERIAL event, making this an information disclosure.
Clamp the loop to field->report_count, the number of value slots the report holds. Value slots past the last declared usage are still scanned; they reuse that usage (HID 1.11, 6.2.2.8).
Verified on v6.12.105 with a UHID reproducer: a 2-byte report from such a descriptor trips KASAN before the patch and not after it.
This page as .md · .json · in your agent: get_signal("CVE-2026-98499")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.