Finding and attribution
In the LE Audio BASE parser, an attacker-controlled Audio_Channel_Allocation LTV length is passed to memcpy into a four-byte stack local in bap_sink_match_allocation(); a second copy exists in bap_sink_get_allocation(). The advisory describes an over-the-air periodic advertisement path within BLE range, without pairing, connection, or user interaction, when the BAP sink and experimental kernel ISO socket path are enabled. With _FORTIFY_SOURCE >= 2 the daemon aborts; with _FORTIFY_SOURCE=0 the source describes a 195-byte-or-greater attacker-controlled write into root-running bluetoothd. The advisory lists no patched release and only proposes checking that the LTV length equals sizeof(uint32_t). Its affected scope is tied to a 2026-04-14 historical master snapshot, not a current exact boundary.
Product: BlueZ. AI system: Claude. Team / organization: Anthropic.
CVE identifiers: Not established in the cited evidence.
AI and human contribution (source account): The BlueZ advisory says this vulnerability was discovered by AI and verified by humans. It credits two named Calif.io researchers working in collaboration with Claude and Anthropic Research. It does not specify the model version or internal discovery date.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The advisory is a public report; it does not establish whether defenders knew of the issue or whether it was exploited before disclosure.
Remediation status: not established. No patched version is listed. The advisory provides a suggested exact-length check for both copies, but does not document a merged patch or released fix. Affected source scope is stated as git master commit 510623fb53b53dce5a297c4a7878cad7546c2e47 from 2026-04-14 and earlier versions containing BAP broadcast-sink code; an exact release boundary is not established.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 27 Aug 2026. AI attribution dated 27 Aug 2026. Sources checked 16 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: High · highest recorded score 7.5. Documented technical effects: denial of service, other.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- Case-level assessment: CVSS 3.1 · 7.5 (High) ·
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H· Assessment scenarios: Narrative CVSS 3.1 line in the advisory; differs from the formal rendered advisory rating.. BlueZ advisory narrative rating · checked 16 Nov 2026. - Case-level assessment: CVSS 3.1 · 3.9 (Low) ·
CVSS:3.1/AV:A/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:L· Assessment scenarios: Formal rendered CVSS 3.1 metrics section in the same advisory; differs from the narrative 7.5 rating.. BlueZ GitHub Advisory rendered rating · checked 16 Nov 2026.
Case-level evidence: denial of service.
Prerequisites / affected scope: For builds with _FORTIFY_SOURCE >= 2, the advisory says malformed periodic advertisement data can abort root-running bluetoothd; systemd auto-restart permits repeated crashes. The BAP sink and experimental ISO path must be enabled; attacker must be within BLE range..
Exploitation evidence: The advisory includes a proof-of-concept artifact and attack-path description but does not report exploitation in the wild.. Impact source · checked 16 Nov 2026.
Case-level evidence: other.
Prerequisites / affected scope: For builds with _FORTIFY_SOURCE=0, the advisory describes a 195-byte-or-greater attacker-controlled stack write beyond a four-byte local in root-running bluetoothd; source does not establish code execution. The BAP sink and experimental ISO path must be enabled; attacker must be within BLE range..
Exploitation evidence: The advisory includes a proof-of-concept artifact and attack-path description but does not report exploitation in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: No patched version is listed. The advisory provides a suggested exact-length check for both copies, but does not document a merged patch or released fix. Affected source scope is stated as git master commit 510623fb53b53dce5a297c4a7878cad7546c2e47 from 2026-04-14 and earlier versions containing BAP broadcast-sink code; an exact release boundary is not established.