CVE-2026-43022: Bluetooth: hci_sync: hci_cmd_sync_queue_once() return -EEXIST if exists
Bluetooth: hcisync: hcicmdsyncqueueonce() return -EEXIST if exists
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.159.1-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.115-2 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.19.12-1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.191 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.160 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.114 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.18.57 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.19.12 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.116-1Fixed in 7.2.15-1Fixed in 7.3.3-1 - Upgrade
Upgrade
ubuntu/linux-nvidia-tegrato a version that resolves this vulnerability.Fixed in 6.8.0-1036.39 - Upgrade
Upgrade
ubuntu/linux-nvidiato a version that resolves this vulnerability.Fixed in 7.0.0-1006.6
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43022?
CVE-2026-43022 has a severity rating that requires attention due to potential impacts on Bluetooth functionality in the Linux kernel.
How do I fix CVE-2026-43022?
To fix CVE-2026-43022, update to the latest version of the Linux kernel that contains the patch for this vulnerability.
What systems are affected by CVE-2026-43022?
CVE-2026-43022 affects systems running vulnerable versions of the Linux kernel that handle Bluetooth operations.
What are the potential impacts of CVE-2026-43022?
The potential impacts of CVE-2026-43022 may include unexpected behavior in Bluetooth connectivity due to improper handling of command synchronization.
Is there a workaround for CVE-2026-43022?
There are no known effective workarounds for CVE-2026-43022, and applying the appropriate security patch is recommended.