CVE-2026-43334High· 8.8▾ TwilightIn the Linux kernel, the following vulnerability has been resolved: Bluetooth: SMP: force responder MITM requirements before building the pairing response smp_cmd_pairing_req() currently builds the pairing response from the initiator a…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 48.4 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.3%
Last analysed / modified upstream
0.3% → 0.3%
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: SMP: force responder MITM requirements before building the pairing response
smp_cmd_pairing_req() currently builds the pairing response from the initiator auth_req before enforcing the local BT_SECURITY_HIGH requirement. If the initiator omits SMP_AUTH_MITM, the response can also omit it even though the local side still requires MITM.
tk_request() then sees an auth value without SMP_AUTH_MITM and may select JUST_CFM, making method selection inconsistent with the pairing policy the responder already enforces.
When the local side requires HIGH security, first verify that MITM can be achieved from the IO capabilities and then force SMP_AUTH_MITM in the response in both rsp.auth_req and auth. This keeps the responder auth bits and later method selection aligned.
Linux >= 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 < 425a22c5373d4e1b46492ab869074ebeeade61f3Linux >= 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 < 7ab69426e7ecbd18a222ee2ec87ca612d30197d7Linux >= 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 < 01bb4045d2306c266178f49ce0c3576d237a3040Linux >= 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 < 91649c02c1baaa18cedf7fb425fa1f0f852c8183Linux >= 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 < c8ff0ca6508535bccabd81c5c9dcc63de8a3d4fbLinux >= 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 < fa14e0e19820b1bbdb42185c9c4efa950bcffef9Linux >= 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 < ec17efb1ef91506cfd17a77692eaf4bbacb520eaLinux >= 2b64d153a0cc9d2b60e47be013cde8490f16e0a5 < d05111bfe37bfd8bd4d2dfe6675d6bdeef43f7c7Linux 3.3Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets