CVE-2026-98499
🟠 MediumLinux kernel. The record carries no CWE from any container and no SSVC decision, and its only references are git.kernel.org stable commits, which are patches rather than advisories, so there is nothing to cite beyond the commit itself, here drivers/hid/wacom_sys.c · From 4.16 onward ; fixed in 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.55, 7.2.9 and 7.3
33.80th percentile
Exploitation
Timeline
- 18/10/2026CVE record published (CVE List)
Risk
AV:A is the unusual part: adjacent-network, no privileges and no user interaction, which for a USB tablet driver reads oddly and is worth treating as an artefact of how the CNA scores HID flaws (no CWE in the record: in the Wacom HID driver, wacom_wac_pen_serial_enforce() reads past the end of a received report when a descriptor lists more usages than its report count, and the value can leak to userspace as an MSC_SERIAL event)Fix
Official description
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.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H