Skip to content
major vulnerability· requires attention

Widely deployed Linux kernel; core infrastructure; Bluetooth flaw affects many environments.

Infrastructure

CVE-2026-43018

8.8
High
EPSS 0.26%Patch availableMay 3, 2026

Linux kernel Bluetooth UAF fix in hci_le_remote_conn_param_req_evt.

common questions

Is CVE-2026-43018 being exploited?

Not confirmed. CVE-2026-43018 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.26% probability of exploitation in the next 30 days.

How severe is CVE-2026-43018?

CVE-2026-43018 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-43018?

Yes. A fix has been recorded for CVE-2026-43018. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-43018 affect?

CVE-2026-43018 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-43018?

Apply the latest kernel update with Bluetooth fix

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (Bluetooth subsystem)
impact

Local memory safety issue in Bluetooth path; unlocked hci_conn usage may cause UAF, kernel crash, or escalation.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 95118dd4edfec950898a00180c6f998df0a6406d and < 59eecf0ffde15670e6a5e10c47be67f73d843b20
  • affected>= 95118dd4edfec950898a00180c6f998df0a6406d and < 5fb69e1eeea9d6cba80517e9f058b56b34bc3a81
  • affected>= 95118dd4edfec950898a00180c6f998df0a6406d and < 7cadb03be37e761130edb153544fe0770a842b19
  • affected>= 95118dd4edfec950898a00180c6f998df0a6406d and < 1d0bdbfe3e91c11f0a704c52443a9446a10d699c
  • affected>= 95118dd4edfec950898a00180c6f998df0a6406d and < ea3cd36d7382d5f8309df04c275d20df139ed42c
  • affected>= 95118dd4edfec950898a00180c6f998df0a6406d and < b255531b27da336571411248c2a72a350662bd09
  • affected5.17
vendor says fixed in< 5.17, >= 6.1.168 and <= 6.1.*, >= 6.6.134 and <= 6.6.*, >= 6.12.81 and <= 6.12.*, >= 6.18.22 and <= 6.18.*, >= 6.19.12 and <= 6.19.*, >= 7.0 and <= *

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free