CVE-2026-43334
Linux kernel Bluetooth pairing MITM policy flaw.
Is CVE-2026-43334 being exploited?
Not confirmed. CVE-2026-43334 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-43334?
CVE-2026-43334 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-43334?
Yes. A fix has been recorded for CVE-2026-43334. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-43334 affect?
CVE-2026-43334 affects Linux kernel Bluetooth subsystem. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-43334?
Apply the Linux kernel Bluetooth patch/update promptly
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
MITM risk during Bluetooth pairing; misalignment could allow interception/modification of data; potential code execution on some setups.
Patch when possible
- affected>= 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 and < 425a22c5373d4e1b46492ab869074ebeeade61f3
- affected>= 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 and < 7ab69426e7ecbd18a222ee2ec87ca612d30197d7
- affected>= 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 and < 01bb4045d2306c266178f49ce0c3576d237a3040
- affected>= 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 and < 91649c02c1baaa18cedf7fb425fa1f0f852c8183
- affected>= 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 and < c8ff0ca6508535bccabd81c5c9dcc63de8a3d4fb
- affected>= 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 and < fa14e0e19820b1bbdb42185c9c4efa950bcffef9
- affected>= 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 and < ec17efb1ef91506cfd17a77692eaf4bbacb520ea
- affected>= 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 and < d05111bfe37bfd8bd4d2dfe6675d6bdeef43f7c7
- affected3.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.