CVE-2026-63916

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

HID: wacom: Fix OOB write in wacom_hid_set_device_mode()

wacom_hid_set_device_mode() currently assumes that the HID_DG_INPUTMODE usage is always located in the first field (field[0]) of the feature report. However, a device can specify HID_DG_INPUTMODE in a different field.

If HID_DG_INPUTMODE is in a field other than the first one and the first field has a report_count smaller than the usage_index of HID_DG_INPUTMODE, this leads to an out-of-bounds write to r->field[0]->value.

Fix this by storing the field index of HID_DG_INPUTMODE in 'struct hid_data' during feature mapping. In wacom_hid_set_device_mode(), use this stored field index to access the correct field and add bounds checks to ensure both the field index and the value index are within valid ranges before writing.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Jul 20, 2026
No patch confirmed yet.
generic

HID: wacom: Fix OOB write in wacom_hid_set_device_mode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ed598de9f61582902406d352d99f2073d8e00298
generic

HID: wacom: Fix OOB write in wacom_hid_set_device_mode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c0a8899e02ddebd51e2589835182c239c2e224ae
generic

HID: wacom: Fix OOB write in wacom_hid_set_device_mode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b8338111e14183972359009c12d0dbd81d2e1e16
generic

HID: wacom: Fix OOB write in wacom_hid_set_device_mode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/83bd8a5756a3c4a413ed8f6253f9eb2821e1ccaf
generic

HID: wacom: Fix OOB write in wacom_hid_set_device_mode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5db3fca0cec7b33bc5379411d0a60d792c9f9bc0
generic

HID: wacom: Fix OOB write in wacom_hid_set_device_mode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5716a293fb19d382ca2336e08fd28a619a5f3c25
generic

HID: wacom: Fix OOB write in wacom_hid_set_device_mode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/43e7c02d6090a82fd60d63491f6871aec906345e
generic

HID: wacom: Fix OOB write in wacom_hid_set_device_mode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2add311d99646c9d235b2c44f9c169ba30f5db3a

Vendor Advisories for CVE-2026-63916(1)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 32× in last 7d / 165× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 215 total refreshes for this CVE.

  1. 2026-08-30 02:57 UTCEG score recompute
  2. 2026-08-30 02:57 UTCVendor advisory
  3. 2026-08-30 02:57 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 23:50 UTCEG score recompute
  7. 2026-08-27 23:50 UTCVendor advisory
  8. 2026-08-27 23:50 UTCGHSA enrichment
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-27 11:54 UTCVendor advisory
  11. 2026-08-27 11:54 UTCGHSA enrichment
  12. 2026-08-26 22:26 UTCEG score recompute
  13. 2026-08-26 22:26 UTCVendor advisory
  14. 2026-08-26 22:26 UTCGHSA enrichment
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-26 07:25 UTCVendor advisory
  17. 2026-08-26 07:25 UTCGHSA enrichment
  18. 2026-08-25 18:49 UTCEG score recompute
  19. 2026-08-25 18:49 UTCGHSA enrichment
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-25 07:00 UTCVendor advisory
  22. 2026-08-25 07:00 UTCGHSA enrichment
  23. 2026-08-24 19:24 UTCEG score recompute
  24. 2026-08-24 19:24 UTCVendor advisory
  25. 2026-08-24 19:24 UTCGHSA enrichment
Show 75 more
  1. 2026-08-24 07:48 UTCVendor advisory
  2. 2026-08-24 07:48 UTCGHSA enrichment
  3. 2026-08-23 20:00 UTCVendor advisory
  4. 2026-08-23 20:00 UTCGHSA enrichment
  5. 2026-08-23 08:23 UTCEG score recompute
  6. 2026-08-23 08:23 UTCVendor advisory
  7. 2026-08-23 08:23 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 20:47 UTCVendor advisory
  10. 2026-08-22 20:47 UTCGHSA enrichment
  11. 2026-08-22 09:11 UTCEG score recompute
  12. 2026-08-22 09:11 UTCVendor advisory
  13. 2026-08-22 09:11 UTCGHSA enrichment
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 21:35 UTCVendor advisory
  16. 2026-08-21 21:35 UTCGHSA enrichment
  17. 2026-08-21 09:59 UTCEG score recompute
  18. 2026-08-21 09:59 UTCVendor advisory
  19. 2026-08-21 09:58 UTCGHSA enrichment
  20. 2026-08-20 22:55 UTCEPSS rescore
  21. 2026-08-20 22:22 UTCVendor advisory
  22. 2026-08-20 22:22 UTCGHSA enrichment
  23. 2026-08-20 10:46 UTCVendor advisory
  24. 2026-08-20 10:46 UTCGHSA enrichment
  25. 2026-08-19 23:10 UTCEG score recompute
  26. 2026-08-19 23:10 UTCVendor advisory
  27. 2026-08-19 23:10 UTCGHSA enrichment
  28. 2026-08-19 17:04 UTCEPSS rescore
  29. 2026-08-19 07:27 UTCVendor advisory
  30. 2026-08-19 07:27 UTCGHSA enrichment
  31. 2026-08-18 19:50 UTCEG score recompute
  32. 2026-08-18 19:50 UTCVendor advisory
  33. 2026-08-18 19:50 UTCGHSA enrichment
  34. 2026-08-18 13:48 UTCEPSS rescore
  35. 2026-08-18 03:41 UTCVendor advisory
  36. 2026-08-18 03:41 UTCGHSA enrichment
  37. 2026-08-17 15:44 UTCEG score recompute
  38. 2026-08-17 15:44 UTCVendor advisory
  39. 2026-08-17 15:44 UTCGHSA enrichment
  40. 2026-08-17 13:47 UTCEPSS rescore
  41. 2026-08-17 04:08 UTCVendor advisory
  42. 2026-08-17 04:08 UTCGHSA enrichment
  43. 2026-08-16 16:32 UTCEG score recompute
  44. 2026-08-16 16:32 UTCVendor advisory
  45. 2026-08-16 16:32 UTCGHSA enrichment
  46. 2026-08-16 14:56 UTCEPSS rescore
  47. 2026-08-16 04:56 UTCEG score recompute
  48. 2026-08-16 04:56 UTCVendor advisory
  49. 2026-08-16 04:56 UTCGHSA enrichment
  50. 2026-08-15 17:20 UTCVendor advisory
  51. 2026-08-15 17:20 UTCGHSA enrichment
  52. 2026-08-15 05:44 UTCEG score recompute
  53. 2026-08-15 05:44 UTCVendor advisory
  54. 2026-08-15 05:44 UTCGHSA enrichment
  55. 2026-08-15 01:30 UTCEPSS rescore
  56. 2026-08-14 18:07 UTCVendor advisory
  57. 2026-08-14 18:07 UTCGHSA enrichment
  58. 2026-08-14 06:31 UTCEG score recompute
  59. 2026-08-14 06:31 UTCVendor advisory
  60. 2026-08-14 06:31 UTCGHSA enrichment
  61. 2026-08-13 22:00 UTCEPSS rescore
  62. 2026-08-13 18:55 UTCVendor advisory
  63. 2026-08-13 18:55 UTCGHSA enrichment
  64. 2026-08-13 07:19 UTCVendor advisory
  65. 2026-08-13 07:19 UTCGHSA enrichment
  66. 2026-08-12 19:28 UTCEG score recompute
  67. 2026-08-12 19:28 UTCVendor advisory
  68. 2026-08-12 19:28 UTCGHSA enrichment
  69. 2026-08-12 13:51 UTCEPSS rescore
  70. 2026-08-12 07:52 UTCVendor advisory
  71. 2026-08-12 07:52 UTCGHSA enrichment
  72. 2026-08-11 20:16 UTCEG score recompute
  73. 2026-08-11 20:16 UTCVendor advisory
  74. 2026-08-11 20:16 UTCGHSA enrichment
  75. 2026-08-11 08:40 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-63916?
CVE-2026-63916 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: HID: wacom: Fix OOB write in wacomhidsetdevicemode() wacomhidsetdevicemode() currently assumes that the HIDDGINPUTMODE usage is always located in the first field (field[0]) of the feature report. However, a device can specify…
When was CVE-2026-63916 disclosed?
CVE-2026-63916 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63916 actively exploited?
CVE-2026-63916 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.8% of all scored CVEs.
What is the CVSS score of CVE-2026-63916?
CVE-2026-63916 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63916?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63916, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63916

Explore →

Is Your Infrastructure Affected by CVE-2026-63916?

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

Start Free Scan →Browse All CVEs