CVE-2026-53209: Bluetooth: hci_sync: reject oversized Broadcast Announcement prepend
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 02f50e8bb69f9b22516163a09922f5537d3b12d1, 10b0e832cc05d7aef4b92bed912cbd4a395d0862, 1338ee049a8910ba6c9cee963920e978e6893c7d; azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 6.6.143.1-1.
Low priority for now. Upgrade to Linux Linux 02f50e8bb69f9b22516163a09922f5537d3b12d1, 10b0e832cc05d7aef4b92bed912cbd4a395d0862, 1338ee049a8910ba6c9cee963920e978e6893c7d; azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 6.6.143.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 25, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-787
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.1.142 and later · before 6.1.176
- linux linux kernel6.6.94 and later · before 6.6.143
- linux linux kernel6.12.34 and later · before 6.12.94
- linux linux kernel6.15.3 and later · before 6.16
- linux linux kernel6.16.1 and later · before 6.18.36
- linux linux kernel6.19 and later · before 7.0.13
- linux linux kernel6.16
- linux linux kernel7.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 15da883c010cbc2a84aec1738b6ad6ee477846de, 6.16affected
- 63f365eb4d1668a04070151b555d55a07ede8d4b and later · before 10b0e832cc05d7aef4b92bed912cbd4a395d0862affected · git
- c621211b308816889f0a3246de448bfcef8ab3ab and later · before 1338ee049a8910ba6c9cee963920e978e6893c7daffected · git
- 907ef6e12fb558a0763e894311eb245a94c192dd and later · before 02f50e8bb69f9b22516163a09922f5537d3b12d1affected · git
- 5725bc608252050ed8a4d47d59225b7dd73474c8 and later · before dafc9f57140e66a10945127aa7433c3d715dc253affected · git
- 5725bc608252050ed8a4d47d59225b7dd73474c8 and later · before cdd8bbdbee763fdf5bf343e6f7d4e79347739f62affected · git
- 5725bc608252050ed8a4d47d59225b7dd73474c8 and later · before 5c65b96b549ea2dcfde497436bf9e048deb87758affected · git
- 6.1.142 and later · before 6.1.176affected · semver
- 6.6.94 and later · before 6.6.143affected · semver
- 6.12.34 and later · before 6.12.94affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-devel-matched | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-debug-modules-extra | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-devel-matched | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-64k-modules-extra | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-cross-headers | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-devel-matched | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
| AlmaLinux:10 | kernel-debug-modules-core | before 6.12.0-211.53.1.el10_2 | 6.12.0-211.53.1.el10_2 |
+96
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-53205Jun 25, 2026 · accel/ivpu: Add bounds checks for firmware log indices28Monitor
- ← EarlierCVE-2026-53208Jun 25, 2026 · Bluetooth: L2CAP: reject BR/EDR signaling packets over MTUsig22Monitor
- Later →CVE-2026-53212Jun 25, 2026 · netfilter: nft_tunnel: fix use-after-free on object destroy31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 02f50e8bb69f9b22516163a09922f5537d3b12d1 | Vendor (CNA) |
| Linux Linux | 10b0e832cc05d7aef4b92bed912cbd4a395d0862 | Vendor (CNA) |
| Linux Linux | 1338ee049a8910ba6c9cee963920e978e6893c7d | Vendor (CNA) |
| Linux Linux | 5c65b96b549ea2dcfde497436bf9e048deb87758 | Vendor (CNA) |
| Linux Linux | 6.1.176 | Vendor (CNA) |
| Linux Linux | 6.12.94 | Vendor (CNA) |
| Linux Linux | 6.16 | Vendor (CNA) |
| Linux Linux | 6.6.143 | Vendor (CNA) |
| Linux Linux | cdd8bbdbee763fdf5bf343e6f7d4e79347739f62 | Vendor (CNA) |
| Linux Linux | dafc9f57140e66a10945127aa7433c3d715dc253 | Vendor (CNA) |
| azl3 kernel 6.6.141.1-1 on Azure Linux 3.0 | 6.6.143.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-core | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-64k-devel-matched | 6.12.0-211.53.1.el10_2 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.1.176-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-211.53.1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
+7
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/10b0e832cc05d7aef4b92bed912cbd4a395d0862
- git.kernel.org/stable/c/1338ee049a8910ba6c9cee963920e978e6893c7d
- git.kernel.org/stable/c/5c65b96b549ea2dcfde497436bf9e048deb87758
- git.kernel.org/stable/c/cdd8bbdbee763fdf5bf343e6f7d4e79347739f62
- git.kernel.org/stable/c/dafc9f57140e66a10945127aa7433c3d715dc253
Vendor advisories and official records. Exploit/PoC links are deliberately left out.