CVE-2026-43022

Analyzed Analyzed - Analysis Complete

Bluetooth: hci_cmd_sync_queue_once() Race Condition in Linux Kernel

Publication date: 2026-05-01

Last updated on: 2026-05-08

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-05-01

Last Modified

2026-05-08

Generated

2026-07-06

AI Q&A

2026-05-01

EPSS Evaluated

2026-07-05

NVD

CVE-2026-43022

EUVD

EUVD-2026-26621

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	6.6.51
linux	linux_kernel	6.1.120
linux	linux_kernel	7.0
linux	linux_kernel	7.0
linux	linux_kernel	7.0
linux	linux_kernel	7.0
linux	linux_kernel	7.0
linux	linux_kernel	7.0
linux	linux_kernel	From 6.9 (inc) to 6.19.12 (exc)
linux	linux_kernel	6.8.9

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability exists in the Linux kernel's Bluetooth subsystem, specifically in the function hci_cmd_sync_queue_once(). The function did not properly indicate whether a queue item was added, which could cause the caller to be unaware if callbacks were called, potentially leading to resource leaks.

The fix changes the function to return -EEXIST if the queue item already exists, allowing the caller to handle this case properly and avoid leaking resources.

Impact Analysis

If exploited or triggered, this vulnerability could cause resource leaks in the Bluetooth subsystem of the Linux kernel. Resource leaks may degrade system performance or stability over time, potentially leading to crashes or denial of service conditions.

Hi! I’m here to help you understand CVE-2026-43022. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70