Skip to main content

Linux Kernel CVE-2026-98499

| EUVDEUVD-2026-103739 HIGH
2026-10-18 Linux GHSA-vgmm-5fmr-gjgq
8.1
CVSS 3.1 · Vendor: Linux
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Attach malicious/emulated HID device
  2. Delivery
    Bind to Wacom pen driver
  3. Exploit
    Send report with over-declared usages
  4. Execution
    Trigger OOB read past report buffer
  5. Impact
    Leak kernel memory via MSC_SERIAL event

Vulnerability Assessment

Exploitation Conditions

Exploitation requires the attacker to present a crafted HID report descriptor in which a field lists more usages than its Report Count reserves (the description cites 12288 usages against Report Count 1), and the device must be handled by the Wacom pen path so that wacom_wac_pen_serial_enforce() processes its reports. The trigger is a short (e.g. 2-byte) report from such a device. Limiting factors: the attacker must be able to attach or emulate a malicious HID peripheral bound by the wacom driver - practically physical access for USB tablets or radio proximity for Bluetooth HID (consistent with AV:A); no authentication (PR:N) and no user interaction beyond device attachment are required, but normal/honest Wacom hardware does not trigger the flaw, so a hostile or spoofed device is essential.

Impact

The CVSS 3.1 base score of 8.1 (AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H) frames this as a high-severity adjacent, unauthenticated flaw, but the signals diverge sharply from that headline. EPSS is only 0.21% (11th percentile), the CVE is not in CISA KEV, and no public exploit reference is supplied - the only references are the kernel.org stable fix commits. The vuln.today decision label is this_week, i.e. prompt patching rather than emergency. Crucially, the mechanism is an out-of-bounds read in the Wacom HID pen driver triggered only when a device presents a malicious HID descriptor (more usages than Report Count reserves); exploitation therefore requires the attacker to supply or emulate a crafted HID peripheral that is bound by the wacom driver. CVSS encodes AV:A (consistent with a Bluetooth HID peripheral), yet for a USB tablet the realistic requirement is physical connection - verify the intended transport, as this materially changes reachability. The impact is a kernel-memory information disclosure (up to ~12 KB past a 2-byte report leaked into wacom_wac->serial[0] and surfaced to userspace as MSC_SERIAL); the A:H likely reflects potential oops/fault on the OOB access rather than a confirmed DoS primitive. Net: a genuine kernel OOB read worth patching on the vendor's this_week cadence, but not a widespread-exploitation emergency - low EPSS, no KEV, and a peripheral-dependent trigger make opportunistic mass exploitation implausible; risk concentrates where untrusted HID devices can be attached.

Exploit ScenarioDerived

An attacker who can attach or emulate an HID peripheral (e.g. a crafted USB tablet, or a Bluetooth HID device within radio range) presents a report descriptor that declares far more usages than its Report Count reserves. When the device sends a short report, wacom_wac_pen_serial_enforce() walks past the field and reads adjacent kernel memory, which is then exposed to userspace as an MSC_SERIAL input event. The description notes a UHID reproducer was used to verify the flaw (KASAN trips before the patch), but no weaponized public exploit is referenced in the input.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 24, 2026

A malicious HID device can trigger an out-of-bounds read in the Linux kernel's Wacom driver when wacom_wac_pen_serial_enforce() walks usage indices past the space its HID report actually reserves. After a hostile device presents a descriptor claiming far more usages than its Report Count holds (the cited case is 12288 usages against Report Count 1), a short 2-byte report makes hid_field_extract() read roughly 12 KB beyond the received buffer; the leaked value lands in wacom_wac->serial[0] and surfaces to userspace as an MSC_SERIAL event, so the impact is information disclosure plus a crash/availability risk. A UHID reproducer verified under KASAN on v6.12.105 confirms the trigger. The flaw requires the attacker to attach or emulate a crafted Wacom-class HID peripheral (physical USB access or Bluetooth HID proximity), which matches the AV:A vector; a public exploit reference exists but is not verified as working exploit code, there is no CISA KEV entry, and EPSS is 0.21% (11th percentile).

RemediationAI

Vendor-released patch: Linux 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, 6.18.55, 7.2.9 and 7.3-rc5, corresponding to stable commits 9aa62f967b6a4bb30aa3b778e02c8a5ca6bcde51, 26471d954bbfbfb9032994f7f485802ee20e0582, 456afe4707e23cc114ad833197f63b52bb8fd1e7, 65e7c4b5366b770c60dfefac3f1d06e33a9e411e, eaa7d29341ef4b91e84ad097562982288a7c376c, c3129e6f26e18c0886ede7265f187a7ec289e1d1, 4b09b7c84b8633cd041181616bd15bf5e73c164d and 9aa237cf66495b2426ddde8532e9b08a0ed83aaa; apply the kernel update for your distribution branch, taking the 6.12.112 or later build where 6.12.105 was reproduced, and reboot to load it. Because the patch clamps the loop to field->report_count, updating is the complete fix; the available sources do not describe any vendor-sanctioned workaround, so interim exposure is governed by whether a hostile HID peripheral can reach a host running the wacom driver, and any decision to block untrusted USB or Bluetooth HID attachment carries the trade-off of disabling legitimate input devices. Advisory links: https://git.kernel.org/stable/c/9aa62f967b6a4bb30aa3b778e02c8a5ca6bcde51 and https://nvd.nist.gov/vuln/detail/CVE-2026-98499.

Affected VersionsENISA

Linux 83417206427bdf0fef9fa69957807194f25923c3 <26471d954bbfbfb9032994f7f485802ee20e0582
Linux 83417206427bdf0fef9fa69957807194f25923c3 <c3129e6f26e18c0886ede7265f187a7ec289e1d1
Linux 4.16
Linux 83417206427bdf0fef9fa69957807194f25923c3 <4b09b7c84b8633cd041181616bd15bf5e73c164d
Linux 83417206427bdf0fef9fa69957807194f25923c3 <456afe4707e23cc114ad833197f63b52bb8fd1e7
Linux patch: 5.10.271
Linux patch: 7.2.9
Linux 83417206427bdf0fef9fa69957807194f25923c3 <eaa7d29341ef4b91e84ad097562982288a7c376c
Linux 83417206427bdf0fef9fa69957807194f25923c3 <9aa237cf66495b2426ddde8532e9b08a0ed83aaa
Linux patch: 7.3-rc5
Linux patch: 6.1.189
Linux 83417206427bdf0fef9fa69957807194f25923c3 <9aa62f967b6a4bb30aa3b778e02c8a5ca6bcde51
Linux patch: 0
Linux patch: 6.6.158
Linux patch: 6.12.112
Linux patch: 5.15.222
Linux patch: 6.18.55
Linux 83417206427bdf0fef9fa69957807194f25923c3 <65e7c4b5366b770c60dfefac3f1d06e33a9e411e

Affected Packages

euvd linux no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The HID subsystem parses report descriptors into hid_report structures, where each field carries a maxusage count derived from the descriptor; hid_field_extract() then pulls values out of the raw report at a computed bit offset. The Wacom pen path calls wacom_wac_pen_serial_enforce() to recover serial numbers, and that function iterated j from 0 to report->field[i]->maxusage rather than the field's report_count. When a descriptor declares more usages than the Report Count reserves, the loop computes offsets for usage slots with no backing data in the report, so hid_field_extract() reads at addresses past the end of the buffer (bit offset 98296, about 12 KB past a 2-byte report, in the described case). The extracted value is written to wacom_wac->serial[0] and can be delivered to userspace as an MSC_SERIAL input event, making the defect an out-of-bounds read with an information-disclosure consequence; KASAN reported the access before the fix. The patch clamps the loop to field->report_count, still scanning value slots past the last declared usage by reusing that usage, as permitted by HID 1.11 section 6.2.2.8. CVSS 3.1 vector AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H reflects adjacent positioning, no privileges, no user interaction, full confidentiality loss and high availability impact, consistent with the crafted-peripheral trigger described here; the underlying CWE was not supplied in the available sources.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Linux) PRIMARY 8.1 HIGH
AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
vuln.today AI 8.1 HIGH

Attacker-supplied HID device needs no credentials (PR:N) or interaction (UI:N); AV:A fits a Bluetooth HID peripheral, with kernel-memory leak (C:H) and potential OOB-read fault (A:H), no integrity impact.

3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
4.0 AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Linux).

CVSS VectorVendor: Linux

Attack Vector
Adjacent
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

Lifecycle Timeline

4
CVSS changed
Oct 24, 2026 - 14:22 NVD
8.1 (HIGH)
Patch available
Oct 18, 2026 - 16:02 EUVD
CVE Published
Oct 18, 2026 - 15:16 cve.org
HIGH 8.1
CVE Published
Oct 18, 2026 - 15:16 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

A high-severity flaw in the Linux kernel's Wacom HID driver allows a malicious or counterfeit peripheral to leak sensitive kernel memory to userspace, potentially exposing secrets and crashing systems. Organizations using Linux endpoints in environments where untrusted USB or Bluetooth HID devices can be connected are at risk of information disclosure and availability disruptions. Leadership should prioritize patching Linux fleets and enforcing device connection policies to mitigate this threat.

Business Impact: Medium
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 89% exploitable
Prevalence
Ubiquitous
Linux kernel runs across nearly all server and device environments
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Controlled
Automatable· derived
No
Human Impact
Medium

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy