Bluetooth: HIDP: validate numbered report payloads
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.265, 5.15.216, 6.1.183, 6.12.103, 6.18.44, 6.6.151, 7.1.8
- CVEs
- CVE-2026-74507
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 8 Nov 2026, 00:22 UTC · Revision 1
Source evidence
Bluetooth: HIDP: validate numbered report payloads
core-osv · Original sourcePublished 15 Aug 2026, 12:27 UTC
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.
osv:CVE-2026-74507
Kernel
Fixed versions: 5.10.265, 5.15.216, 6.1.183, 6.6.151, 6.12.103, 6.18.44, 7.1.8
Complete source record
{
"id": "7d9d8166f27bcd5389b78aad6d5ca31ddb5acfc84d1b43b06e7a5b2227c75251",
"url": "https://osv.dev/vulnerability/CVE-2026-74507",
"method": "structured",
"payload": {
"kind": "advisory",
"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 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.",
"evidence": "osv:CVE-2026-74507",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.265",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.216",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.183",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.151",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.103",
"evidence": "/affected/1/ranges"
},
{
"value": "6.18.44",
"evidence": "/affected/1/ranges"
},
{
"value": "7.1.8",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2026-74507",
"aliases": [
"CVE-2026-74507"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "0ff1731a1ae51e8e48cd559d70db536281c47f8e"
},
{
"fixed": "011bf4350d941f1995b2bd4b815ee206cacf2b8e"
},
{
"fixed": "689d8bb7fee96b7196b572b015b6055c6616ce0c"
},
{
"fixed": "c73beb320f5705e508bf7d385b8cc5ef8d9c8b69"
},
{
"fixed": "b7ad105d46acd828e424454815e4cd31069e047a"
},
{
"fixed": "7e7162427659b70ea17cd41b1f79e2e64c246690"
},
{
"fixed": "27cc0e603355c585f1e5da8398faa4d36d498188"
},
{
"fixed": "9c841f59e10b5d75c398a3fc6b2da448d2a2276b"
},
{
"fixed": "34f53d27b81a16a02828c8fdfa4e02badc326f17"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-74507.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "2.6.39"
},
{
"fixed": "5.10.265"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.216"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.183"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.151"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.103"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.18.44"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.1.8"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-74507.json"
}
}
],
"modified": "2026-10-28T02:30:52.110635893Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/011bf4350d941f1995b2bd4b815ee206cacf2b8e",
"https://git.kernel.org/stable/c/27cc0e603355c585f1e5da8398faa4d36d498188",
"https://git.kernel.org/stable/c/34f53d27b81a16a02828c8fdfa4e02badc326f17",
"https://git.kernel.org/stable/c/689d8bb7fee96b7196b572b015b6055c6616ce0c",
"https://git.kernel.org/stable/c/7e7162427659b70ea17cd41b1f79e2e64c246690",
"https://git.kernel.org/stable/c/9c841f59e10b5d75c398a3fc6b2da448d2a2276b",
"https://git.kernel.org/stable/c/b7ad105d46acd828e424454815e4cd31069e047a",
"https://git.kernel.org/stable/c/c73beb320f5705e508bf7d385b8cc5ef8d9c8b69",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/74xxx/CVE-2026-74507.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-74507",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/74xxx/CVE-2026-74507.json"
}
},
"related_cves": [
{
"value": "CVE-2026-74507",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 520932,
"published_at": "2026-08-15T12:27:30.683+00:00"
}