CVE-2026-74509

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-15. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: hci_sync: Fix advertising data UAFs

hci_find_adv_instance() returns an adv_info pointer that is valid only while hdev->lock is held. The advertising command-sync paths perform instance lookups without that lock and, in some cases, retain the pointer while waiting for a controller response.

An advertising termination event can therefore interleave as follows:

hci_cmd_sync_work hci_rx_work hci_find_adv_instance() __hci_cmd_sync_status() wait for controller reply hci_dev_lock() hci_remove_adv_instance() kfree(adv) adv->scan_rsp_changed = false

KASAN reported:

BUG: KASAN: slab-use-after-free in hci_set_ext_scan_rsp_data_sync+0x2e1/0x300 Write of size 1 at addr ffff88810a45d21d by task kworker/u17:0/88 Workqueue: hci0 hci_cmd_sync_work Call Trace: hci_set_ext_scan_rsp_data_sync+0x2e1/0x300 hci_schedule_adv_instance_sync+0x390/0x4c0 hci_cmd_sync_work+0x173/0x300 Allocated by task 87: hci_add_adv_instance+0x538/0xac0 add_advertising+0x885/0x1160 Freed by task 89: kfree+0x131/0x3c0 hci_remove_adv_instance+0x1d8/0x3b0 hci_le_ext_adv_term_evt+0x17b/0x730

Protect the instance lookup and payload construction in the extended advertising, scan response, and periodic advertising data paths. Snapshot the advertising parameters under hdev->lock, but release the lock before waiting for the controller.

Clear advertising-data dirty bits before issuing their commands and restore them after a failure using a fresh lookup. Likewise, update the reported transmit power through a fresh lookup after the parameter command completes. No adv_info pointer then survives an HCI command wait.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (4)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

Bluetooth: hci_sync: Fix advertising data UAFs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eb1d8318764de7216e6dbba29a24d69f7ce51348
generic

Bluetooth: hci_sync: Fix advertising data UAFs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cdc36db204ffd97b947d64374cf23a210dc74777
generic

Bluetooth: hci_sync: Fix advertising data UAFs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b16ebdbebd2d37f4cdc590bc3e9db71fe90350a3
generic

Bluetooth: hci_sync: Fix advertising data UAFs - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/95cdcd8c82a501931fd3ae9b3811b0b6da167e94

Vendor Advisories for CVE-2026-74509(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 30× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 05:45 UTCEG score recompute
  2. 2026-08-21 05:45 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 17:57 UTCGHSA enrichment
  5. 2026-08-20 06:10 UTCGHSA enrichment
  6. 2026-08-19 18:22 UTCEG score recompute
  7. 2026-08-19 18:22 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-19 06:20 UTCGHSA enrichment
  10. 2026-08-18 18:33 UTCEG score recompute
  11. 2026-08-18 18:32 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 06:44 UTCGHSA enrichment
  15. 2026-08-17 18:54 UTCEG score recompute
  16. 2026-08-17 18:54 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 06:24 UTCEG score recompute
  19. 2026-08-17 06:24 UTCGHSA enrichment
  20. 2026-08-17 05:55 UTCEG score recompute 8.80
  21. 2026-08-17 05:55 UTCGHSA enrichment
  22. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  23. 2026-08-17 05:39 UTCEG score recompute
  24. 2026-08-17 05:39 UTCGHSA enrichment
  25. 2026-08-17 05:39 UTCMITRE cvelistV5
Show 5 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-15 13:27 UTCNVD update
  4. 2026-08-15 12:39 UTCEG score recompute
  5. 2026-08-15 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74509?
CVE-2026-74509 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_sync: Fix advertising data UAFs hcifindadvinstance() returns an advinfo pointer that is valid only while hdev->lock is held. The advertising command-sync paths perform instance lookups without that lock and, in some…
When was CVE-2026-74509 disclosed?
CVE-2026-74509 was first published in the National Vulnerability Database on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74509 actively exploited?
CVE-2026-74509 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.3% of all scored CVEs.
What is the CVSS score of CVE-2026-74509?
CVE-2026-74509 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-74509?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74509, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-74509

Explore →

Is Your Infrastructure Affected by CVE-2026-74509?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.