Skip to content
Systems

CVE-2026-74509

8.8
High
EPSS 0.25%Patch availableAug 17, 2026

Linux Bluetooth HCI use-after-free in advertising paths causing kernel memory corruption

common questions

Is CVE-2026-74509 being exploited?

Not confirmed. CVE-2026-74509 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-74509?

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

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

What does CVE-2026-74509 affect?

CVE-2026-74509 affects Linux kernel (Bluetooth HCI: hci_sync, adv/scan/periodic advertising), Bluetooth-enabled Linux servers/workstations, Embedded/IoT devices using affected kernels, Android kernels without patch. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74509?

Apply vendor/upstream Linux kernel updates; restrict/disable Bluetooth until patched.

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

executive summary
technical analysis
affected
Linux kernel (Bluetooth HCI: hci_sync, adv/scan/periodic advertising)Bluetooth-enabled Linux servers/workstationsEmbedded/IoT devices using affected kernelsAndroid kernels without patch
impact

Bluetooth advertising UAF can cause kernel memory corruption, crashes, and may allow local/nearby attackers to achieve privilege escalation or kernel code execution.

action required

Immediate action required

affected versions
Linux Linux
  • affected>= cba6b758711cab946c787f7c15be92cc749b8e1f and < 565971488191bf54a87a417abafab6ad0de72201
  • affected>= cba6b758711cab946c787f7c15be92cc749b8e1f and < c4cec575a6d6f7c36808a3a0017b0675968bb06b
  • affected>= cba6b758711cab946c787f7c15be92cc749b8e1f and < 95cdcd8c82a501931fd3ae9b3811b0b6da167e94
  • affected>= cba6b758711cab946c787f7c15be92cc749b8e1f and < eb1d8318764de7216e6dbba29a24d69f7ce51348
  • affected>= cba6b758711cab946c787f7c15be92cc749b8e1f and < b16ebdbebd2d37f4cdc590bc3e9db71fe90350a3
  • affected>= cba6b758711cab946c787f7c15be92cc749b8e1f and < cdc36db204ffd97b947d64374cf23a210dc74777
  • affected42fe380baaaccbe635c34ca07b29d19b9ec2498d
  • affected>= 5.15.210 and < 5.16
  • affected5.17
vendor says fixed in< 5.17, >= 6.1.184 and <= 6.1.*, >= 6.6.154 and <= 6.6.*, >= 6.12.103 and <= 6.12.*, >= 6.18.44 and <= 6.18.*, >= 7.1.8 and <= 7.1.*, >= 7.2 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