Bluetooth: MGMT: reject HCI_CMD_SYNC params_len above 255
Summary
| CVE | CVE-2026-80760 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-09-04 16:18:01 UTC |
| Updated | 2026-09-04 16:18:01 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: reject HCI_CMD_SYNC params_len above 255 mgmt_hci_cmd_sync() checks that the message length agrees with params_len but puts no upper bound on it. params_len is __le16 while the parameter length in the HCI command header is a u8: struct hci_command_hdr { __le16 opcode; __u8 plen; } __packed; hci_cmd_sync_alloc() assigns one to the other: hdr->plen = plen; if (plen) skb_put_data(skb, param, plen); so a params_len of 256 leaves plen at 0 while all 256 bytes are still appended. The frame handed to the driver then declares no parameters and carries 256 of them. On a length framed transport such as H:4 the controller takes the trailing bytes as the start of the next packet. The mgmt socket MTU is HCI_MAX_FRAME_SIZE, so params_len can reach about 1KB this way. Commit 03f1700b9b4d ("Bluetooth: MGMT: reject malformed HCI_CMD_SYNC commands") only made params_len agree with the message length, a value that fits the message but not the header field is still accepted. Reject params_len that does not fit the header field. |
Risk And Classification
EPSS: 0.001680000 probability, percentile 0.063130000 (date 2026-09-07)
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected 827af4787e74e8df9e8e0677a69fbb15e0856d2f b7d9edcf9fe6e9ec3a2e80ef9e8d44ef9b4f2894 git | Not specified |
| CNA | Linux | Linux | affected 827af4787e74e8df9e8e0677a69fbb15e0856d2f 0bd0195ce25737cbdd0eabc54319ee0ddf3a0ad2 git | Not specified |
| CNA | Linux | Linux | affected 827af4787e74e8df9e8e0677a69fbb15e0856d2f 6e1c44878aa3ee7336efeaf01414b030b0a5c273 git | Not specified |
| CNA | Linux | Linux | affected 827af4787e74e8df9e8e0677a69fbb15e0856d2f 5d95286b6d6e8f1d304da7522bfa6860fc017e48 git | Not specified |
| CNA | Linux | Linux | affected 6.13 | Not specified |
| CNA | Linux | Linux | unaffected 6.13 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.47 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.1.11 7.1.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.1 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3-rc1 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/0bd0195ce25737cbdd0eabc54319ee0ddf3a0ad2 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/5d95286b6d6e8f1d304da7522bfa6860fc017e48 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/6e1c44878aa3ee7336efeaf01414b030b0a5c273 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/b7d9edcf9fe6e9ec3a2e80ef9e8d44ef9b4f2894 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.