CVE-2026-99489: Linux kernel · HID: wacom: Redesign shared sibling data lifecycle
Source GCVE Database
Not known to be exploited · fixed in f1fb9f9087c76bca6de81aa38e1e9c820dc54744 : patch Linux kernel soon.
Data as of 19 Nov 2026, 17:19 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in f1fb9f9087c76bca6de81aa38e1e9c820dc54744, 480c9cb14ae81f8e112ff83f8778b3d7b9324dc8, 321da540c4a2091c0e23b5f4ced0131a1c77d679 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 Linux kernel to f1fb9f9087c76bca6de81aa38e1e9c820dc54744, 480c9cb14ae81f8e112ff83f8778b3d7b9324dc8, 321da540c4a2091c0e23b5f4ced0131a1c77d679 or 4eeb0a16f11c72a0a15e793310470418d1c2d3cd.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A redesign of the Wacom driver's shared sibling data lifecycle has been implemented to eliminate the Use-After-Free condition. The fix includes removing the volatile pointer, storing stable static copies of device attributes, and improving synchronization with mutexes. Users should apply the official Linux kernel updates that include this fix once available.
Description
A Use-After-Free vulnerability was identified and resolved in the Linux kernel's Wacom driver. The issue stemmed from improper management of a volatile pointer used for sibling device matching, which could lead to dereferencing a dangling pointer after device disconnection. The fix involved redesigning the data lifecycle to use stable static copies of device attributes and improving synchronization to prevent race conditions during device probe and removal.
References
- nvd.nist.gov/vuln/detail/CVE-2026-99489 (opens in a new tab)
- git.kernel.org/stable/c/321da540c4a2091c0e23b5f4ced0131a1c77d679 (opens in a new tab)
- git.kernel.org/stable/c/480c9cb14ae81f8e112ff83f8778b3d7b9324dc8 (opens in a new tab)
- git.kernel.org/stable/c/4eeb0a16f11c72a0a15e793310470418d1c2d3cd (opens in a new tab)
- git.kernel.org/stable/c/f1fb9f9087c76bca6de81aa38e1e9c820dc54744 (opens in a new tab)