PoC Monitor
← All CVEs
CVE-2026-98499published 18 Oct 2026 15:16 UTCData: JSON · API

Linux

HID: wacom: fix OOB read in wacom_wac_pen_serial_enforce()

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.

First public PoC 20 daysafter publication · 7 Nov 2026
Public PoCs11 on GitHub
CVSS8.1high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 83417206427bdf0fef9fa69957807194f25923c3, < 9aa62f967b6a4bb30aa3b778e02c8a5ca6bcde51
  • >= 83417206427bdf0fef9fa69957807194f25923c3, < 26471d954bbfbfb9032994f7f485802ee20e0582
  • >= 83417206427bdf0fef9fa69957807194f25923c3, < 456afe4707e23cc114ad833197f63b52bb8fd1e7
  • >= 83417206427bdf0fef9fa69957807194f25923c3, < 65e7c4b5366b770c60dfefac3f1d06e33a9e411e
  • >= 83417206427bdf0fef9fa69957807194f25923c3, < eaa7d29341ef4b91e84ad097562982288a7c376c
  • >= 83417206427bdf0fef9fa69957807194f25923c3, < c3129e6f26e18c0886ede7265f187a7ec289e1d1
  • >= 83417206427bdf0fef9fa69957807194f25923c3, < 4b09b7c84b8633cd041181616bd15bf5e73c164d
  • >= 83417206427bdf0fef9fa69957807194f25923c3, < 9aa237cf66495b2426ddde8532e9b08a0ed83aaa

Fixed in 9aa62f967b6a4bb30aa3b778e02c8a5ca6bcde51, 26471d954bbfbfb9032994f7f485802ee20e0582, 456afe4707e23cc114ad833197f63b52bb8fd1e7, 65e7c4b5366b770c60dfefac3f1d06e33a9e411e, eaa7d29341ef4b91e84ad097562982288a7c376c, c3129e6f26e18c0886ede7265f187a7ec289e1d1, 4b09b7c84b8633cd041181616bd15bf5e73c164d, 9aa237cf66495b2426ddde8532e9b08a0ed83aaa

Linux Linux
  • 4.16

Fixed in 0, 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.55, 7.2.9, 7.3

Mitigation

Upgrade Linux to 9aa62f967b6a4bb30aa3b778e02c8a5ca6bcde51 or 26471d954bbfbfb9032994f7f485802ee20e0582 or 456afe4707e23cc114ad833197f63b52bb8fd1e7 or 65e7c4b5366b770c60dfefac3f1d06e33a9e411e or eaa7d29341ef4b91e84ad097562982288a7c376c or c3129e6f26e18c0886ede7265f187a7ec289e1d1 or 4b09b7c84b8633cd041181616bd15bf5e73c164d or 9aa237cf66495b2426ddde8532e9b08a0ed83aaa or later.

Upgrade Linux to 0 or 5.10.271 or 5.15.222 or 6.1.189 or 6.6.158 or 6.12.112 or 6.18.55 or 7.2.9 or 7.3 or later.

Timeline

Days relative to CVE publication
-3t=0+3+6+9+12+15+18+21CVE published18 Oct 2026 · t = 0First public PoC7 Nov 2026 · t+20d

First public PoC 20 days after publication; not in CISA KEV. First PoC: woshigenm/CVE-2026-98499 (created 7 Nov 2026, found by us: 14 Nov 2026).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedFound by usStarsAssessment
woshigenm/CVE-2026-98499 7 Nov 2026 +20 d 14 Nov 2026 3 PoC
Flags · score 15
  • no network code found (normal for a local exploit)

Below the suspicion threshold (50); does not change the assessment.

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.