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-53209Bluetooth: hci_sync: reject oversized Broadcast Announcement prepend

Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: reject oversized Broadcast Announcement prepend Existing advertising instances can already hold the maximum extended advertising payload. When hci_adv_bcast_annoucement() prepends the Broadcast Announcement service data to that payload, the combined data may no longer fit in the temporary buffer used to rebuild the advertising data. Reject that case before copying the existing payload and report the failure through the device log. This keeps the existing advertising data intact and avoids overrunning the temporary buffer.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 4 months 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

CVSS scores of CVE-2026-53209, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 63f365eb4d1668a04070151b555d55a07ede8d4b – < 10b0e832cc05d7aef4b92bed912cbd4a395d0862
    • affected c621211b308816889f0a3246de448bfcef8ab3ab – < 1338ee049a8910ba6c9cee963920e978e6893c7d
    • affected 907ef6e12fb558a0763e894311eb245a94c192dd – < 02f50e8bb69f9b22516163a09922f5537d3b12d1
    • affected 5725bc608252050ed8a4d47d59225b7dd73474c8 – < dafc9f57140e66a10945127aa7433c3d715dc253
    • affected 5725bc608252050ed8a4d47d59225b7dd73474c8 – < cdd8bbdbee763fdf5bf343e6f7d4e79347739f62
    • affected 5725bc608252050ed8a4d47d59225b7dd73474c8 – < 5c65b96b549ea2dcfde497436bf9e048deb87758
    • affected 15da883c010cbc2a84aec1738b6ad6ee477846de
    • affected 6.1.142 – < 6.1.176
    • affected 6.6.94 – < 6.6.143
    • affected 6.12.34 – < 6.12.94
    • affected 6.15.3 – < 6.16
  • Linux · Linux

    • affected 6.16
    • unaffected < 6.16
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.94 – ≤ 6.12.*
    • unaffected 6.18.36 – ≤ 6.18.*
    • unaffected 7.0.13 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .