CVE-2026-64433

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2026-48777 (ENISA EUVD) · GHSA-g2v2-wh7x-5cmc (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

Bluetooth: MGMT: Fix UAF of hci_conn_params in add_device_complete

add_device_complete() runs from the hci_cmd_sync_work kworker, which holds only hci_req_sync_lock and *not* hci_dev_lock. It calls hci_conn_params_lookup() and then dereferences the returned object (params->flags) without taking hci_dev_lock:

params = hci_conn_params_lookup(hdev, &cp->addr.bdaddr, le_addr_type(cp->addr.type)); ... device_flags_changed(NULL, hdev, &cp->addr.bdaddr, cp->addr.type, hdev->conn_flags, params ? params->flags : 0);

hci_conn_params_lookup() walks hdev->le_conn_params and is documented to require hdev->lock. A concurrent MGMT_OP_REMOVE_DEVICE (remove_device()), which does run under hci_dev_lock, can call hci_conn_params_free() to list_del() and kfree() the very object the lookup returned, so the subsequent params->flags read touches freed memory [0].

Hold hci_dev_lock() across the hci_conn_params_lookup() and the read of params->flags (and the matching event emission) so the lookup result cannot be freed by a concurrent remove_device() before it is used, honouring the locking contract of hci_conn_params_lookup().

[0]: (trailing page/memory-state dump trimmed) BUG: KASAN: slab-use-after-free in add_device_complete+0x358/0x3d8 net/bluetooth/mgmt.c:7671 Read of size 1 at addr ffff000017ab26c1 by task kworker/u9:8/388

CPU: 1 UID: 0 PID: 388 Comm: kworker/u9:8 Not tainted 7.0.11 #20 PREEMPT Hardware name: linux,dummy-virt (DT) Workqueue: hci0 hci_cmd_sync_work Call trace: show_stack+0x2c/0x3c arch/arm64/kernel/stacktrace.c:499 (C) __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0xb4/0xd4 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0x118/0x5d8 mm/kasan/report.c:482 kasan_report+0xb0/0xf4 mm/kasan/report.c:595 __asan_report_load1_noabort+0x20/0x2c mm/kasan/report_generic.c:378 add_device_complete+0x358/0x3d8 net/bluetooth/mgmt.c:7671 hci_cmd_sync_work+0x14c/0x240 net/bluetooth/hci_sync.c:334 process_one_work+0x628/0xd38 kernel/workqueue.c:3289 process_scheduled_works kernel/workqueue.c:3372 [inline] worker_thread+0x7a8/0xac0 kernel/workqueue.c:3453 kthread+0x39c/0x444 kernel/kthread.c:436 ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860

Allocated by task 3401: kasan_save_stack+0x3c/0x64 mm/kasan/common.c:57 kasan_save_track+0x20/0x3c mm/kasan/common.c:78 kasan_save_alloc_info+0x40/0x54 mm/kasan/generic.c:570 poison_kmalloc_redzone mm/kasan/common.c:398 [inline] __kasan_kmalloc+0xd4/0xd8 mm/kasan/common.c:415 kasan_kmalloc include/linux/kasan.h:263 [inline] __kmalloc_cache_noprof+0x1b0/0x458 mm/slub.c:5385 kmalloc_noprof include/linux/slab.h:950 [inline] kzalloc_noprof include/linux/slab.h:1188 [inline] hci_conn_params_add+0x10c/0x4b0 net/bluetooth/hci_core.c:2279 hci_conn_params_set net/bluetooth/mgmt.c:5162 [inline] add_device+0x5b4/0xa54 net/bluetooth/mgmt.c:7755 hci_mgmt_cmd net/bluetooth/hci_sock.c:1721 [inline] hci_sock_sendmsg+0x10b4/0x1dd0 net/bluetooth/hci_sock.c:1841 sock_sendmsg_nosec net/socket.c:727 [inline] __sock_sendmsg+0xe0/0x128 net/socket.c:742 sock_write_iter+0x250/0x390 net/socket.c:1195 new_sync_write fs/read_write.c:595 [inline] vfs_write+0x66c/0xab0 fs/read_write.c:688 ksys_write+0x1fc/0x24c fs/read_write.c:740 __do_sys_write fs/read_write.c:751 [inline] __se_sys_write fs/read_write.c:748 [inline] __arm64_sys_write+0x70/0xa4 fs/read_write.c:748 __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline] invoke_syscall+0x84/0x2a8 arch/arm64/kernel/syscall.c:49 el0_svc_common.constprop.0+0xe4/0x294 arch/arm64/kernel/syscall.c:132 do_el0_svc+0x44/0x5c arch/arm64/kernel/syscall.c:151 el0_svc+0x38/0xac arch/arm64/kernel/entry-common.c:724 el0t_64_sync_handler+0xa0/0xe4 arch/arm64/kernel/entry-common.c:743 el0t_64_sync+0x198/0x19c arch/arm64/kernel/entry.S:596

Freed by task 3740: kasan_save_stack+0x3c/0x64 ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-06). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 25, 2026

Last Modified

November 6, 2026

Advisory Details (5)

Auto-updated Sep 3, 2026
Patch available.
Web page

Bluetooth: MGMT: Fix UAF of hci_conn_params in add_device_complete - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fa85d985f614bc3feb343000f14a1072e99b0df1
Web page

Bluetooth: MGMT: Fix UAF of hci_conn_params in add_device_complete - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e4369e4e970f3fa4676b76be14c1d315c87f22b6
Web page

Bluetooth: MGMT: Fix UAF of hci_conn_params in add_device_complete - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/caed4a96d55757c139a899744657c032b6186665
Web page

Bluetooth: MGMT: Fix UAF of hci_conn_params in add_device_complete - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b346efa825b5e4386f19bc63f81141652d496ec4
Web page

Bluetooth: MGMT: Fix UAF of hci_conn_params in add_device_complete - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9531014c60c804e16099885d4a98aedcf31bce8d

Vendor Advisories for CVE-2026-64433(2)

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

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-10-28ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-10-28ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-10-28ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-28ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1019.19) @ resolute2026-10-28ubuntu
ubuntulinux-virtual-6.8 (6.8.0-147.147) @ noble2026-10-28ubuntu
ubuntulinux-tools-ibm-7.0 (7.0.0-1013.13) @ resolute2026-10-28ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2018.18) @ resolute2026-10-28ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18) @ resolute2026-10-28ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1011.11) @ resolute2026-10-28ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-28ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1071.79) @ noble2026-10-28ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-28ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.12—
  • every version up to 6.12.100-1~deb12u1: fixed in 6.12.100-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)
  • every version up to 6.12.96-1: fixed in 6.12.96-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (162 versions)
  • every version up to 7.1.4-1: fixed in 7.1.4-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(13)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 238 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 138 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-11-06 17:27 UTCVendor advisory
  7. 2026-11-06 17:27 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-11-06 16:53 UTCEchelonGraph re-scored
  9. 2026-11-06 16:53 UTCVendor advisory
  10. 2026-11-06 16:53 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  11. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-11-04 15:37 UTCEchelonGraph re-scored
  15. 2026-11-04 15:37 UTCVendor advisory
  16. 2026-11-04 15:37 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-28 07:55 UTCEchelonGraph re-scored
  25. 2026-10-28 07:55 UTCVendor advisory
Show 75 more
  1. 2026-10-28 07:55 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  2. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-25 14:12 UTCEchelonGraph re-scored
  5. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-20 19:23 UTCEchelonGraph re-scored
  10. 2026-10-20 19:23 UTCVendor advisory
  11. 2026-10-20 19:23 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-10-18 03:22 UTCEchelonGraph re-scored
  16. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  21. 2026-10-13 11:41 UTCEchelonGraph re-scored
  22. 2026-10-13 11:41 UTCVendor advisory
  23. 2026-10-13 11:41 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-10-12 15:48 UTCEchelonGraph re-scored
  26. 2026-10-11 19:32 UTCEchelonGraph re-scored
  27. 2026-10-11 16:47 UTCEchelonGraph re-scored
  28. 2026-10-11 14:09 UTCEchelonGraph re-scored
  29. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  30. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  31. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  32. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  33. 2026-10-07 04:26 UTCEchelonGraph re-scored
  34. 2026-10-07 04:26 UTCVendor advisory
  35. 2026-10-07 04:26 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  36. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  37. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  38. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  39. 2026-10-04 07:29 UTCEchelonGraph re-scored
  40. 2026-10-04 07:29 UTCVendor advisory
  41. 2026-10-04 07:29 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  42. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  43. 2026-10-02 18:33 UTCEchelonGraph re-scored
  44. 2026-10-02 18:33 UTCVendor advisory
  45. 2026-10-02 18:33 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  46. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  47. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  48. 2026-10-01 15:45 UTCVendor advisory
  49. 2026-10-01 15:45 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  50. 2026-10-01 04:02 UTCEchelonGraph re-scored
  51. 2026-10-01 04:02 UTCVendor advisory
  52. 2026-10-01 04:02 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  53. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  54. 2026-09-29 08:01 UTCEchelonGraph re-scored
  55. 2026-09-29 08:01 UTCVendor advisory
  56. 2026-09-29 08:00 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  57. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  58. 2026-09-28 04:09 UTCEchelonGraph re-scored
  59. 2026-09-28 04:09 UTCVendor advisory
  60. 2026-09-28 04:09 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  61. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  62. 2026-09-25 07:40 UTCEchelonGraph re-scored
  63. 2026-09-25 07:40 UTCVendor advisory
  64. 2026-09-25 07:40 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  65. 2026-09-24 09:46 UTCVendor advisory
  66. 2026-09-24 09:45 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-09-23 22:08 UTCEchelonGraph re-scored
  68. 2026-09-23 22:08 UTCVendor advisory
  69. 2026-09-23 22:07 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  71. 2026-09-23 09:36 UTCVendor advisory
  72. 2026-09-23 09:35 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8
  73. 2026-09-22 21:58 UTCEchelonGraph re-scored
  74. 2026-09-22 21:58 UTCVendor advisory
  75. 2026-09-22 21:58 UTCGHSA enrichmentGHSA-g2v2-wh7x-5cmc · GitHub severity HIGH · GitHub CVSS 7.8

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64433?
CVE-2026-64433 is a high-severity vulnerability; its CVE record was published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: Fix UAF of hci_conn_params in add_device_complete add_device_complete() runs from the hci_cmd_sync_work kworker, which holds only hci_req_sync_lock and not hci_dev_lock. It calls hci_conn_params_lookup() and then…
When was the CVE record for CVE-2026-64433 published?
The CVE record for CVE-2026-64433 was published on July 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 6, 2026; the record at its source may have been updated since.
Is CVE-2026-64433 actively exploited?
CVE-2026-64433 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64433?
CVE-2026-64433 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-64433?
A fix for CVE-2026-64433 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64433 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64433

Explore →

Is Your Infrastructure Affected by CVE-2026-64433?

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

Book a Demo →Browse All CVEs