CVE-2026-74507

CVE CVE-2026-74507EUVD EUVD-2026-59700Published 2026-08-15T12:27:30.000ZLast changed 2026-08-19T16:38:05.000ZCVSS 7.1

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 0ff1731a1ae51e8e48cd559d70db536281c47f8e <34f53d27b81a16a02828c8fdfa4e02badc326f17; patch: 6.6.151; patch: 6.18.44; patch: 5.15.216; 0ff1731a1ae51e8e48cd559d70db536281c47f8e <9c841f59e10b5d75c398a3fc6b2da448d2a2276b; 2.6.39; 0ff1731a1ae51e8e48cd559d70db536281c47f8e <7e7162427659b70ea17cd41b1f79e2e64c246690; patch: 6.12.103; patch: 7.1.8; patch: 5.10.265; 0ff1731a1ae51e8e48cd559d70db536281c47f8e <011bf4350d941f1995b2bd4b815ee206cacf2b8e; 0ff1731a1ae51e8e48cd559d70db536281c47f8e <689d8bb7fee96b7196b572b015b6055c6616ce0c; patch: 0; patch: 6.1.183; 0ff1731a1ae51e8e48cd559d70db536281c47f8e <c73beb320f5705e508bf7d385b8cc5ef8d9c8b69; patch: 7.2; 0ff1731a1ae51e8e48cd559d70db536281c47f8e <27cc0e603355c585f1e5da8398faa4d36d498188; 0ff1731a1ae51e8e48cd559d70db536281c47f8e <b7ad105d46acd828e424454815e4cd31069e047a

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.