Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80760Bluetooth: MGMT: reject HCI_CMD_SYNC params_len above 255

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 45 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 827af4787e74e8df9e8e0677a69fbb15e0856d2f – < b7d9edcf9fe6e9ec3a2e80ef9e8d44ef9b4f2894
    • affected 827af4787e74e8df9e8e0677a69fbb15e0856d2f – < 0bd0195ce25737cbdd0eabc54319ee0ddf3a0ad2
    • affected 827af4787e74e8df9e8e0677a69fbb15e0856d2f – < 6e1c44878aa3ee7336efeaf01414b030b0a5c273
    • affected 827af4787e74e8df9e8e0677a69fbb15e0856d2f – < 5d95286b6d6e8f1d304da7522bfa6860fc017e48
  • Linux · Linux

    • affected 6.13
    • unaffected < 6.13
    • unaffected 6.18.47 – ≤ 6.18.*
    • unaffected 7.1.11 – ≤ 7.1.*
    • unaffected 7.2.1 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80760 badge
[![CVE-2026-80760](https://cveledger.app/badge/CVE-2026-80760.svg)](https://cveledger.app/cve/CVE-2026-80760)

Record last updated .