CVE-2026-43022
Description
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: hci_sync: hci_cmd_sync_queue_once() return -EEXIST if exists
hci_cmd_sync_queue_once() needs to indicate whether a queue item was added, so caller can know if callbacks are called, so it can avoid leaking resources.
Change the function to return -EEXIST if queue item already exists.
Modify all callsites to handle that.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A fix in the Linux kernel's Bluetooth hci_sync changes hci_cmd_sync_queue_once() to return -EEX return -EEXIST when a command is already queued, preventing resource leaks.
The vulnerability exists in the Linux kernel's Bluetooth subsystem, specifically in the hci_cmd_sync_queue_once() function within hci_sync. The function was not reliably indicating whether a command queue item already existed, potentially leading to resource leaks if callers were unaware of duplicate entries. The patch changes the function to return -EEXIST when the item is already present, allowing callers to avoid duplicating resources [1][2].
To exploit this issue, an attacker would need to trigger a scenario where a Bluetooth command is submitted multiple times, causing the kernel to allocate resources (e.g., memory) that are not properly freed. Since this is a logic flaw in the queue management, a local user with the ability to interact with the Bluetooth stack (e.g., via certain operations) could potentially cause a denial of service by repeatedly sending commands, leading to resource exhaustion.
The impact is primarily a denial-of-service condition where repeated duplicate command queues can exhaust kernel memory, resulting in system instability or crashes. There is no indication of privilege escalation or information disclosure. The patch ensures that hci_cmd_sync_queue_once() returns -EEXIST when a duplicate is found, and all callsites are updated to handle this return value appropriately, thus preventing the leak [1][2].
Mitigation is available through the kernel update that includes this commit. Users should apply the patch from the stable kernel tree to resolve the issue. There is no indication that this vulnerability is under active exploit or listed in KEV.
AI Insight generated on May 18, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
10cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*+ 9 more
- cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*range: >=6.9,<6.19.12
- cpe:2.3:o:linux:linux_kernel:6.1.120:*:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:6.6.51:*:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:6.8.9:*:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:7.0:rc1:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:7.0:rc2:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:7.0:rc3:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:7.0:rc4:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:7.0:rc5:*:*:*:*:*:*
- cpe:2.3:o:linux:linux_kernel:7.0:rc6:*:*:*:*:*:*
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
2News mentions
1- Patch Tuesday - May 2026Rapid7 Blog · May 13, 2026