CVE-2026-43051

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 0

A fix is available — apply it.

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

HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq

The wacom_intuos_bt_irq() function processes Bluetooth HID reports without sufficient bounds checking. A maliciously crafted short report can trigger an out-of-bounds read when copying data into the wacom structure.

Specifically, report 0x03 requires at least 22 bytes to safely read the processed data and battery status, while report 0x04 (which falls through to 0x03) requires 32 bytes.

Add explicit length checks for these report IDs and log a warning if a short report is received.

CVSS v3
8.1
EG Score
8.1(medium)
EPSS
17.1%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 7, 2026

Advisory Details (8)

Auto-updated May 3, 2026
No patch confirmed yet.
generic

HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq - kernel/git/stable/linux.git - Linux kernel stable tree

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

HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq - kernel/git/stable/linux.git - Linux kernel stable tree

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

HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq - kernel/git/stable/linux.git - Linux kernel stable tree

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

HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8bd690ac1242332c73cba10dacdad6c6642bbb94
generic

HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq - kernel/git/stable/linux.git - Linux kernel stable tree

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

HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/41026bcc0fdf82605205c27935ef719cbc07193b
generic

HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3d78386b144453c47e81bf62dc3601b757f02d99
generic

HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-43051(4)

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
redhatkernel-0:6.12.0-211.18.1.el10_22026-05-28redhat
redhatkernel-rt-0:4.18.0-553.126.1.rt7.467.el8_102026-05-28redhat
redhatkernel-0:4.18.0-553.126.1.el8_102026-05-28redhat
redhatkernel-0:5.14.0-687.12.1.el9_82026-05-28redhat
linuxKernel @ 5.10.253—osv

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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 133 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43051?
CVE-2026-43051 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: HID: wacom: fix out-of-bounds read in wacomintuosbt_irq The wacomintuosbt_irq() function processes Bluetooth HID reports without sufficient bounds checking. A maliciously crafted short report can trigger an out-of-bounds read when…
When was CVE-2026-43051 disclosed?
CVE-2026-43051 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43051 actively exploited?
CVE-2026-43051 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 17.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43051?
CVE-2026-43051 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-43051?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43051, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-43051?

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

Start Free Scan →Browse All CVEs