Skip to main content
VulnerabilityPublished

CVE-2026-99491: Linux kernel · HID: wacom: Fix Use-After-Free in wacom_intuos_pad

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ef32877368a7013c060ef6bd03a30b6da2fe0c41 : patch Linux kernel soon.

Data as of 19 Nov 2026, 15:35 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in ef32877368a7013c060ef6bd03a30b6da2fe0c41, ef74a8a685e272dbe0d21844c6e70841ccc9b1bc, 1178927ffa54a1f9e52fa4e5974862023237fce6 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=3.13.8 <3.14
Fixed in
  • ef32877368a7013c060ef6bd03a30b6da2fe0c41
  • ef74a8a685e272dbe0d21844c6e70841ccc9b1bc
  • 1178927ffa54a1f9e52fa4e5974862023237fce6
  • 4e1bf2f5fe28cb8719aee7ca9d99ea529224ed1f
  • 3.14
LinuxLinuxAffected
  • =3.14
Fixed in–

AI-suggested

The vulnerability is fixed in Linux kernel version 3.14 and specific commits identified by hashes. Users should upgrade to Linux kernel 3.14 or later versions containing the fix. No additional mitigation is required as the patch fully addresses the race condition and use-after-free issue.

Description

A use-after-free vulnerability in the Linux kernel's wacom driver (wacom_intuos_pad) was fixed. The issue arises from a race condition where the touch_input pointer is accessed without proper locking in interrupt context, leading to potential dereferencing of freed memory. The fix introduces RCU (Read-Copy-Update) protection to safely manage the touch_input pointer and serializes concurrent probe assignments to prevent state desynchronization.

References

Community reviews

Loading reviews…