CVE-2026-99491

UNRATEDCVSS · not yet scoredElevated

Also known asEUVD-2026-130166 (ENISA EUVD) · GHSA-2mq8-33hp-8j6v (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictPlan a fixWithin your standard update timelines — no confirmed exploitation yet.
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS v2: —Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

HID: wacom: Fix Use-After-Free in wacom_intuos_pad

wacom_intuos_pad() accesses wacom->shared->touch_input locklessly inside the interrupt handler context. If the Touch sibling device is disconnected, wacom_remove_shared_data() clears 'touch_input' outside any lock, creating a Time-of-Check to Time-of-Use (TOCTOU) race condition where a preempted reader in interrupt context dereferences the freed pointer, leading to a Use-After-Free.

Resolve this by introducing RCU protection for the touch_input pointer:

  • Annotate 'touch_input' in wacom_shared struct with __rcu
  • Wrap all lockless readers in wacom_wac.c with guard(rcu)() and
rcu_dereference() using a unified wacom_report_touch_mute() helper
  • Update writers in wacom_sys.c using rcu_assign_pointer()
  • Call synchronize_rcu() in wacom_remove_shared_data() to ensure
all active RCU readers have finished before the input device is freed

Also wrap wacom_set_shared_values() and touch/pen assignments in wacom_add_shared_data() inside the wacom_udev_list_lock to serialize concurrent probe assignments, and verify that 'shared->touch == hdev' before setting touch_input to prevent concurrent sibling probe state desynchronization.

CVSS
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.3%
EPSS %ILE
19th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 19, 2026

Last Modified

November 19, 2026

Vendor Advisories for CVE-2026-99491(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 5× in last 7d / 5× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-11-19 16:03 UTCENISA EUVD ID recordedEUVD-2026-130166 · Source: ENISA EUVD
  4. 2026-11-19 15:49 UTCGHSA enrichmentGHSA-2mq8-33hp-8j6v
  5. 2026-11-19 14:48 UTCEchelonGraph re-scored
  6. 2026-11-19 14:48 UTCMITRE cvelistV5first tracked

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (3 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • GitHub PoCwoshigenm/CVE-2026-99491-FANXIAOCHAO
    Published Nov 22, 2026

    CVE-2026-99491 — Android 17 / 6.12.58 wacom HID sibling touch_input UAF: uhid-based LPE with three modes, uid-0 shell and optional temporary KernelSU. GPL-2.0-only.

    Open source ↗
  • GitHub PoCYunnijian/CVE-2026-99491
    Published Nov 21, 2026
    Open source ↗
  • GitHub PoCwoshigenm/CVE-2026-99491
    Published Nov 20, 2026

    CVE-2026-99491 — wacom HID sibling UAF LPE (uhid → KernelSU temp root), 5.15 EXP.

    Open source ↗

Frequently asked(4)

What is CVE-2026-99491?
CVE-2026-99491 is a vulnerability whose severity is not yet rated; its CVE record was published on November 19, 2026. In the Linux kernel, the following vulnerability has been resolved: HID: wacom: Fix Use-After-Free in wacom_intuos_pad wacom_intuos_pad() accesses wacom->shared->touch_input locklessly inside the interrupt handler context. If the Touch sibling device is disconnected, wacom_remove_shared_data()…
When was the CVE record for CVE-2026-99491 published?
The CVE record for CVE-2026-99491 was published on November 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 19, 2026; the record at its source may have been updated since.
Is CVE-2026-99491 actively exploited?
CVE-2026-99491 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-99491?
A fix for CVE-2026-99491 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-99491 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-99491

Explore →

Is Your Infrastructure Affected by CVE-2026-99491?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.