Skip to main content
Mallory
UnratedVulnerability

CVE-2026-85218: Double stack-based buffer overflow in BlueZ AVRCP ListPlayerAttributes handling

Updated 12 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 2 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-85218CWE-121

CVE-2026-85218 is a double stack-based buffer overflow in the BlueZ AVRCP controller implementation. A nearby Bluetooth BR/EDR peripheral can supply a crafted AVRCP player-settings response containing an attacker-controlled attribute count. The avrcp_list_player_attributes_rsp() and avrcp_get_current_player_value() functions can consequently write attacker-controlled data beyond fixed-size stack buffers. Exploitation can crash the bluetoothd daemon and may permit arbitrary code execution. Out-of-bounds memory access may also expose sensitive information.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can corrupt stack memory and crash bluetoothd, disrupting Bluetooth services. Arbitrary code execution may be possible with the privileges of the daemon, depending on exploitability and runtime protections. Sensitive information disclosure is also a potential consequence of the out-of-bounds memory access. Code execution is a potential outcome rather than a demonstrated capability; no known exploits are identified.

Mitigation

If you can’t patch tonight, do this now.

Disable Bluetooth or AVRCP/media-control functionality where operationally feasible until corrected packages are deployed. Otherwise, restrict Bluetooth pairing and use, and minimize interactions with untrusted Bluetooth peripherals.

Remediation

Patch, then assume compromise.

Install distribution-provided BlueZ updates addressing CVE-2026-85218. For Ubuntu, prefer the regression-corrected packages from USN-8908-2: 5.85-4ubuntu0.4 for 26.04 LTS, 5.72-0ubuntu5.8 for 24.04 LTS, 5.64-0ubuntu1.6 for 22.04 LTS, and 5.53-0ubuntu3.9+esm2 for 20.04 LTS. USN-8908-1 supplies 5.48-0ubuntu3.9+esm3 for Ubuntu 18.04 LTS and 5.37-0ubuntu5.3+esm6 for 16.04 LTS. Ubuntu 20.04 and 18.04 fixes require Ubuntu Pro; the 16.04 fix additionally requires Legacy Support. Fedora identifies bluez-5.87+1.git8750129efca8-1.fc43 and bluez-5.87+1.git8750129efca8-1.fc45 as corrective builds, subject to promotion into the applicable update repositories. Apply the corresponding security updates for TencentOS Server 4 and TuxCare-supported AlmaLinux and Rocky Linux releases. RHEL 9 and 10 are identified as unpatched; fixed RHEL package versions are not available in the supplied information.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-85218 exploited in the wild?
As of Nov 10, 2026, Mallory has no reports of CVE-2026-85218 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-85218?
As of Nov 10, 2026, Mallory has found no public exploit for CVE-2026-85218.
Is there a patch for CVE-2026-85218?
Install distribution-provided BlueZ updates addressing CVE-2026-85218. For Ubuntu, prefer the regression-corrected packages from USN-8908-2: 5.85-4ubuntu0.4 for 26.04 LTS, 5.72-0ubuntu5.8 for 24.04 LTS, 5.64-0ubuntu1.6 for 22.04 LTS, and 5.53-0ubuntu3.9+esm2 for 20.04 LTS.
Activity feed

Recent activity

14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 9, 2026TencentOS Server 4: bluez (TSSA-2026:1341) | Tenable®A double stack-based buffer overflow in BlueZ affects the bluez package on TencentOS Server 4. Crafted AVRCP player-settings responses from a nearby Bluetooth BR/EDR peripheral can trigger out-of-bounds stack writes in avrcp_list_player_attributes_rsp() and avrcp_get_current_player_value() in profiles/audio/avrcp.c. Successful exploitation could crash bluetoothd or execute code. The advisory lists a CVSS v3 base score of 7.1 and provides package updates under TSSA-2026:1341. Nessus identifies affected installations using self-reported version information rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Oct 30, 2026Rocky Linux 9.6 [TuxCare] Security Update: bluez / bluez-cups ... | Tenable®A double stack overflow in BlueZ AVRCP ListPlayerAttributes handling involving avrcp_list_player_attributes_rsp and avrcp_get_current_player_value. The advisory identifies Rocky Linux 9.6 packages as affected but does not describe exploitation prerequisites or specific impacts for this flaw.Read more ↗tenable nessus pluginsNews · Oct 30, 2026AlmaLinux 9.6 [TuxCare] Security Update: bluez / bluez-cups / ... | Tenable®A double stack-buffer overflow affecting BlueZ AVRCP ListPlayerAttributes handling in avrcp_list_player_attributes_rsp and avrcp_get_current_player_value. The advisory identifies AlmaLinux 9.6 BlueZ packages as affected but provides no further exploitation prerequisites or impact details.Read more ↗tenable nessus pluginsNews · Oct 20, 2026AlmaLinux 9.2 [TuxCare] Security Update: bluez / bluez-cups / ... | Tenable®A double stack-overflow vulnerability affects BlueZ AVRCP ListPlayerAttributes handling in avrcp_list_player_attributes_rsp and avrcp_get_current_player_value. The content does not specify exploitation prerequisites or resulting impacts. Updated packages are available for AlmaLinux 9.2.Read more ↗
+8 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.