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-80763Bluetooth: hci_event: validate LE Set CIG Parameters response

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_event: validate LE Set CIG Parameters response The Command Complete dispatch validates only the fixed part of the LE Set CIG Parameters response. After that part is pulled from the skb, hci_cc_le_set_cig_params() trusts num_handles and reads each entry in the trailing handle array. Matching num_handles against the command's num_cis does not guarantee that the response contains the advertised handles. A truncated response from a malfunctioning controller can therefore make the handler read beyond the skb data. Validate that the remaining skb data contains all advertised handles. Include this in the existing response validation so malformed responses also follow the established CIG failure handling.

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.17% · top 93% of all CVEs (17 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 26afbd826ee326e63a334c37fd45e82e50a615ec – < 9e05783d0bb96a7b853cc058a7c7de2dc4a62154
    • affected 26afbd826ee326e63a334c37fd45e82e50a615ec – < 26741d178f31932c9018b36b7953e6dc391436a4
    • affected 26afbd826ee326e63a334c37fd45e82e50a615ec – < a34df5c4a439cfc04565fa5be608ed1e53134f1f
    • affected 26afbd826ee326e63a334c37fd45e82e50a615ec – < e3f82e8f2a5915f533b57a065e9a045aa2ee03bc
    • affected 26afbd826ee326e63a334c37fd45e82e50a615ec – < d83ecb7b96105d932dabaa56ccd7418c25fb7cbb
    • affected 26afbd826ee326e63a334c37fd45e82e50a615ec – < 6fc540e835dddb518cef3ff522b780f701cd03df
    • affected 26afbd826ee326e63a334c37fd45e82e50a615ec – < 0acd4eeb4b225b9bebbf9ef96cc10cdd79b94899
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.1.187 – ≤ 6.1.*
    • unaffected 6.6.154 – ≤ 6.6.*
    • unaffected 6.12.106 – ≤ 6.12.*
    • unaffected 6.18.47 – ≤ 6.18.*
    • unaffected 7.1.11 – ≤ 7.1.*
    • unaffected 7.2.1 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .