CVE-2026-74508

CVE CVE-2026-74508EUVD EUVD-2026-59701Published 2026-08-15T12:27:31.000ZLast changed 2026-08-19T16:38:07.000ZCVSS 8.8

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: HIDP: reject frames without a transaction header hidp_recv_ctrl_frame() and hidp_recv_intr_frame() read skb->data[0] before checking that the L2CAP SDU contains a transaction header. A connected HIDP peer can send an empty basic-mode SDU and make both paths use an uninitialized byte from skb tailroom. KMSAN reports the use in hidp_session_run(), with the uninitialized value originating in __alloc_skb() through vhci_write(). The control path produces two reports and the interrupt path produces one. The byte can also be controlled by a malformed lower-layer packet. If an HCI ACL packet contains an L2CAP PDU with a declared zero-length payload followed by an extra 0x15 byte, l2cap_recv_acldata() reduces skb->len to the declared PDU length before dispatch. The current HIDP path nevertheless consumes the extra byte as HIDP_TRANS_HID_CONTROL | HIDP_CTRL_VIRTUAL_CABLE_UNPLUG and terminates the HIDP session. With this change, the same packet is discarded and a subsequent feature report request succeeds. Pull the transaction header with skb_pull_data() and discard frames that do not contain it.

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 patch: 5.15.216; patch: 6.6.151; patch: 7.2; patch: 7.1.8; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2ebf63aa557a69990b4e9ea22be224d58aabce96; patch: 0; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <47778d2c2087b5d192398f6fddf692d16a5431cf; 2.6.12; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <854194494a6f726a60b90b76059148bf08df023d; patch: 6.1.183; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <97b61241ab45bfa5b0526cb0f3978942493bc811; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <238c333bc4b3f245c626632e8bfa3c9dab97f51b; patch: 6.18.44; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <46ca5ab39737d7c6f9ca77ecf714cdcfa6caaeec; patch: 6.12.103; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <567a2a0a633f2ea5fdccaf3517c09f22c9d860c7

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

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

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.