---
id: CVE-2026-74507
title: 'Bluetooth: HIDP: validate numbered report payloads'
summary: |-
  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…
severity: high
cvss: 7.1
cvssVector: 'CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N'
cvssSource: cna
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e <
    011bf4350d941f1995b2bd4b815ee206cacf2b8e
  - >-
    Linux >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e <
    689d8bb7fee96b7196b572b015b6055c6616ce0c
  - >-
    Linux >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e <
    c73beb320f5705e508bf7d385b8cc5ef8d9c8b69
  - >-
    Linux >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e <
    b7ad105d46acd828e424454815e4cd31069e047a
  - >-
    Linux >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e <
    7e7162427659b70ea17cd41b1f79e2e64c246690
  - >-
    Linux >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e <
    27cc0e603355c585f1e5da8398faa4d36d498188
  - >-
    Linux >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e <
    9c841f59e10b5d75c398a3fc6b2da448d2a2276b
  - >-
    Linux >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e <
    34f53d27b81a16a02828c8fdfa4e02badc326f17
  - Linux 2.6.39
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-10-16T18:58:31.395135Z'
published: '2026-08-15'
updated: '2026-10-16'
sourceUpdated: '2026-10-16T19:05:51.043Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-74507'
references:
  - url: 'https://git.kernel.org/stable/c/011bf4350d941f1995b2bd4b815ee206cacf2b8e'
  - url: 'https://git.kernel.org/stable/c/689d8bb7fee96b7196b572b015b6055c6616ce0c'
  - url: 'https://git.kernel.org/stable/c/c73beb320f5705e508bf7d385b8cc5ef8d9c8b69'
  - url: 'https://git.kernel.org/stable/c/b7ad105d46acd828e424454815e4cd31069e047a'
  - url: 'https://git.kernel.org/stable/c/7e7162427659b70ea17cd41b1f79e2e64c246690'
  - url: 'https://git.kernel.org/stable/c/27cc0e603355c585f1e5da8398faa4d36d498188'
  - url: 'https://git.kernel.org/stable/c/9c841f59e10b5d75c398a3fc6b2da448d2a2276b'
  - url: 'https://git.kernel.org/stable/c/34f53d27b81a16a02828c8fdfa4e02badc326f17'
tags:
  - cve.org
epss: 0.00242
epssPercentile: 0.14331
ingestedAt: '2026-10-16T19:46:24.352Z'
---

## Overview

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.

## Affected

- `Linux >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e < 011bf4350d941f1995b2bd4b815ee206cacf2b8e`
- `Linux >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e < 689d8bb7fee96b7196b572b015b6055c6616ce0c`
- `Linux >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e < c73beb320f5705e508bf7d385b8cc5ef8d9c8b69`
- `Linux >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e < b7ad105d46acd828e424454815e4cd31069e047a`
- `Linux >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e < 7e7162427659b70ea17cd41b1f79e2e64c246690`
- `Linux >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e < 27cc0e603355c585f1e5da8398faa4d36d498188`
- `Linux >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e < 9c841f59e10b5d75c398a3fc6b2da448d2a2276b`
- `Linux >= 0ff1731a1ae51e8e48cd559d70db536281c47f8e < 34f53d27b81a16a02828c8fdfa4e02badc326f17`
- `Linux 2.6.39`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.