# CVE-2026-43051: HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq

> A maliciously crafted Bluetooth HID report can trigger an out-of-bounds read in the Linux kernel's Wacom driver, potentially causing a crash or leaking memory.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 May 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-43051, DEBIAN-CVE-2026-43051, GHSA-4mjh-m2x6-5qg4, ROOT-OS-DEBIAN-11-CVE-2026-43051, ROOT-OS-UBUNTU-2204-CVE-2026-43051, ROOT-OS-UBUNTU-2404-CVE-2026-43051, UBUNTU-CVE-2026-43051

## What is CVE-2026-43051?

CVE-2026-43051 is a high-severity memory corruption vulnerability in Linux kernel, published on 1 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-43051?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-43051?

Apply the vendor's patch.

## Is CVE-2026-43051 being exploited?

There is no known exploitation of CVE-2026-43051 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-43051 and fix it if it is affected.

What it is: CVE-2026-43051 is a high-severity memory corruption vulnerability in Linux kernel, published on 1 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-43051 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-43051/ (Markdown: https://insights.sbomify.com/CVE-2026-43051/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-43051
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-43051
- OSV: https://osv.dev/vulnerability/CVE-2026-43051

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-43051/
Summaries are generated and may contain mistakes; the official description above is the record.