CVE-2026-74507

Bluetooth: HIDP: validate numbered report payloads

State: Published
Severity: 7.1 High
Published: Aug 15, 2026
Updated: Oct 16, 2026
Reserved: Aug 15, 2026

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.

Scores

CVSS	Score	Vector	Source
3.1	7.1 High	CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N	Linux

Weaknesses

The record names no weakness.

Affected Products

Product	Versions
LinuxLinux	0ff1731a1ae51e8e48cd559d70db536281c47f8e to before 011bf4350d941f1995b2bd4b815ee206cacf2b8eAffected 0ff1731a1ae51e8e48cd559d70db536281c47f8e to before 689d8bb7fee96b7196b572b015b6055c6616ce0cAffected 0ff1731a1ae51e8e48cd559d70db536281c47f8e to before c73beb320f5705e508bf7d385b8cc5ef8d9c8b69Affected 0ff1731a1ae51e8e48cd559d70db536281c47f8e to before b7ad105d46acd828e424454815e4cd31069e047aAffected 0ff1731a1ae51e8e48cd559d70db536281c47f8e to before 7e7162427659b70ea17cd41b1f79e2e64c246690Affected 0ff1731a1ae51e8e48cd559d70db536281c47f8e to before 27cc0e603355c585f1e5da8398faa4d36d498188Affected 0ff1731a1ae51e8e48cd559d70db536281c47f8e to before 9c841f59e10b5d75c398a3fc6b2da448d2a2276bAffected 0ff1731a1ae51e8e48cd559d70db536281c47f8e to before 34f53d27b81a16a02828c8fdfa4e02badc326f17Affected
LinuxLinux	2.6.39Affected before 2.6.39Not affected 5.10.265 through 5.10.Not affected 5.15.216 through 5.15.Not affected 6.1.183 through 6.1.Not affected 6.6.151 through 6.6.Not affected 6.12.103 through 6.12.Not affected 6.18.44 through 6.18.Not affected 7.1.8 through 7.1.*Not affected 7.2 and laterNot affected

Product

Versions

LinuxLinux

0ff1731a1ae51e8e48cd559d70db536281c47f8e to before 011bf4350d941f1995b2bd4b815ee206cacf2b8eAffected
0ff1731a1ae51e8e48cd559d70db536281c47f8e to before 689d8bb7fee96b7196b572b015b6055c6616ce0cAffected
0ff1731a1ae51e8e48cd559d70db536281c47f8e to before c73beb320f5705e508bf7d385b8cc5ef8d9c8b69Affected
0ff1731a1ae51e8e48cd559d70db536281c47f8e to before b7ad105d46acd828e424454815e4cd31069e047aAffected
0ff1731a1ae51e8e48cd559d70db536281c47f8e to before 7e7162427659b70ea17cd41b1f79e2e64c246690Affected
0ff1731a1ae51e8e48cd559d70db536281c47f8e to before 27cc0e603355c585f1e5da8398faa4d36d498188Affected
0ff1731a1ae51e8e48cd559d70db536281c47f8e to before 9c841f59e10b5d75c398a3fc6b2da448d2a2276bAffected
0ff1731a1ae51e8e48cd559d70db536281c47f8e to before 34f53d27b81a16a02828c8fdfa4e02badc326f17Affected

LinuxLinux

2.6.39Affected
before 2.6.39Not affected
5.10.265 through 5.10.*Not affected
5.15.216 through 5.15.*Not affected
6.1.183 through 6.1.*Not affected
6.6.151 through 6.6.*Not affected
6.12.103 through 6.12.*Not affected
6.18.44 through 6.18.*Not affected
7.1.8 through 7.1.*Not affected
7.2 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.