CVE-2026-85036

The Bluetooth Classic AVDTP layer defers releasing a session's stream endpoints: bt_avdtp_l2cap_disconnected() in subsys/bluetooth/host/classic/avdtp.c ends with k_work_submit(&session->_release_work), placing the embedded struct k_work on the system work queue's pending list. When the same struct bt_avdtp object is immediately reused for a new signalling connection, the session memory is re-initialized — a2dp_get_connection() in subsys/bluetooth/host/classic/a2dp.c memset()s the whole struct bt_a2dp, and bt_avdtp_l2cap_accept() / bt_avdtp_connect() call k_work_init() on session->_release_work — while that work item is still linked into k_sys_work_q.pending. Zeroing a linked sys_snode_t truncates the list while its tail pointer keeps pointing past the truncation. The reuse window is deterministic rather than a race. All host RX processing runs on the Bluetooth RX work queue at a cooperative priority (CONFIG_BT_RX_PRIO), while _release_work is submitted to the lower-priority system work queue, so the release handler cannot run until the RX thread blocks. Because l2cap_br_recv() processes every signalling command contained in a single L2CAP signalling PDU back-to-back, a peer can send one PDU holding an L2CAP Disconnection Request for the AVDTP signalling channel followed by a Connection Request for PSM 0x0019; the second command reaches the session-reuse path with the release work provably still queued. The peer must already hold an encrypted AVDTP signalling channel, i.e. be a paired/bonded BR/EDR device. The result is corruption of the global system work queue's pending list: either the queue silently stops executing any work at all (subsequent submissions are appended to a chain the head can no longer reach, and the orphaned items keep their K_WORK_QUEUED flag forever) or, in the tail variant, the list acquires a self-referencing node that the queue thread spins on. The written values are pointers to other struct k_work objects and are not attacker-controlled, so the impact is a device-wide, reboot-required denial of service rather than a controllable write primitive. Only builds with CONFIG_BT_CLASSIC and CONFIG_BT_A2DP are affected. The fix is a two-commit unit, and neither commit closes the path on its own. ec822ceed83b adds a pending-release check to bt_avdtp_connect() and bt_avdtp_l2cap_accept(), but the A2DP upper layer's a2dp_get_connection() memset()s the session — including the queued work item's list node and flags — before those checks run, so k_work_busy_get() would observe an already-cleared state. 2bd5ea88c69b closes that by making a2dp_get_connection() itself skip the reuse and return NULL while the release work is still pending, which both callers already handle by rejecting the connection attempt. Apply both commits together; either one alone leaves the device vulnerable.

Score
CVSS 3.1 5.7 Medium
Status
Awaiting Analysis - vulnerabilities@zephyrproject.org
Published
2026-11-04
Last modified
2026-11-09
Weaknesses
CWE-666

Affected products

References


Your early warning system for new security vulnerabilities


Open BETA

Every day brings a flood of new vulnerabilities, roughly 100 CVEs daily. Which one will really affect you?

Attacks on known but unpatched vulnerabilities (Common Vulnerabilities and Exposures, or CVEs for short) are among the most common entry points for hackers. Companies must continuously check for such vulnerabilities. Does this affect our products? Which versions are affected? How critical is it?

As the window between publication and exploitation by attackers keeps shrinking, companies are under more pressure than ever to find a high-quality solution for managing these risks as quickly as possible. However, IT teams are heavily time-constrained, making manual tracking of all relevant CVEs nearly impossible.

100+ new CVEs per day

Most CVEs are irrelevant to your infrastructure

Time-to-exploit < 5 days

Attackers are exploiting vulnerabilities faster than ever before

Manual research is time-consuming

Vendor websites, RSS feeds, and blogs need to be searched daily

Vulnerability scanners are lagging behind

Plugin development isn't progressing fast enough to identify risks in a timely manner

CVE Alarm provides you with immediate notifications of relevant security vulnerabilities

CVE Alarm continuously monitors all newly published CVEs and automatically compares them with the products you use. You will only be notified if a relevant vulnerability affects your systems and meets your defined criteria.

Real-time notification

Direct email notification without delay

Product-based filters

Only CVEs that actually affect your infrastructure

Custom criteria

Filter by CVSS-Score, exposure, products, and vendors

Team-oriented & multi-tenant capable

Assign products or alerts to specific teams or customers

More time to act

Administrators can review and install updates faster

Time savings

No more manually reviewing the flood of new CVE information

Three steps for better patch planning

With CVE Alarm you will easily receive relevant security alerts for your infrastructure.

Subscribe To
Products

Select the IT products you use. From Apache to VMware – all critical assets are monitored.

Define
Criteria

Set product-specific filters based on criticality (CVSS ≥ 7.0 (high)). You will only receive relevant alerts.

Get
Notified

Receive an immediate notification as soon as a matching CVE appears. Recipients can be defined individually for each product.

Be faster
than the attackers

With CVE information, you have more time for patch planning and can close security gaps before they are exploited.

Designed for the target group companies and service providers

Whether a global Security Operations Center or a small IT team, CVE Alarm supports CVE monitoring for organizations of all sizes.

Companies with their own IT infrastructure

Medium-sized to large companies that need to proactively monitor their vulnerabilities

Administrators

IT professionals responsible for infrastructure security and maintenance

Security teams and cybersecurity experts

Security Operations Centers (SOCs) and Computer Emergency Response Teams (CERTs) that require CVE information for proactive security measures

Chief Information Security Officers (CISOs) & IT managers

Decision-makers who need an overview of critical vulnerabilities

Security service providers

Managed service providers (MSPs) and security consultancies that manage multiple clients and need to monitor CVEs

From experience to innovation. About us and CVE Alarm.

CVE Alarm is a product of AVABIS GmbH and was developed in collaboration with IT security experts.

AVABIS GmbH – Who are we?
We, AVABIS GmbH, are an experienced partner for IT quality assurance. Our focus is on software testing and software development. Our clients, corporations from various industries, have trusted us for more than ten years.

CVE Alarm – How did the idea come about?
In our daily project work, we repeatedly witnessed the significant uncertainty surrounding new security alerts. We saw how much time teams have to invest to determine whether a published vulnerability even affects their own system landscape. Based on these experiences, we know how time-consuming it is to gather, evaluate, and prioritize information from diverse sources under time pressure.

This made us realize that the real problem is not a lack of information, but rather an overabundance of it.

This led to the idea of ​​developing a product that enables companies to manage this information overload and maintain control over their IT security.

Developed and operated in Germany
Our systems run on German IT infrastructure, and we adhere to high security and data protection standards. This ensures data sovereignty, clear responsibilities, and reliability, especially for organizations with their own security teams or CERT structures.

Get in contact with our team

Do you have questions about CVE Alarm or would you like a personal consultation?
We're happy to help.

Please use our contact form.