CVE-2026-43322

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-08. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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

A fix is available — apply it.

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

Bluetooth: hci_sync: Fix UAF in le_read_features_complete

This fixes the following backtrace caused by hci_conn being freed before le_read_features_complete but after hci_le_read_remote_features_sync so hci_conn_del -> hci_cmd_sync_dequeue is not able to prevent it:

================================================================== BUG: KASAN: slab-use-after-free in instrument_atomic_read_write include/linux/instrumented.h:96 [inline] BUG: KASAN: slab-use-after-free in atomic_dec_and_test include/linux/atomic/atomic-instrumented.h:1383 [inline] BUG: KASAN: slab-use-after-free in hci_conn_drop include/net/bluetooth/hci_core.h:1688 [inline] BUG: KASAN: slab-use-after-free in le_read_features_complete+0x5b/0x340 net/bluetooth/hci_sync.c:7344 Write of size 4 at addr ffff8880796b0010 by task kworker/u9:0/52

CPU: 0 UID: 0 PID: 52 Comm: kworker/u9:0 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025 Workqueue: hci0 hci_cmd_sync_work Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1f0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xcd/0x630 mm/kasan/report.c:482 kasan_report+0xe0/0x110 mm/kasan/report.c:595 check_region_inline mm/kasan/generic.c:194 [inline] kasan_check_range+0x100/0x1b0 mm/kasan/generic.c:200 instrument_atomic_read_write include/linux/instrumented.h:96 [inline] atomic_dec_and_test include/linux/atomic/atomic-instrumented.h:1383 [inline] hci_conn_drop include/net/bluetooth/hci_core.h:1688 [inline] le_read_features_complete+0x5b/0x340 net/bluetooth/hci_sync.c:7344 hci_cmd_sync_work+0x1ff/0x430 net/bluetooth/hci_sync.c:334 process_one_work+0x9ba/0x1b20 kernel/workqueue.c:3257 process_scheduled_works kernel/workqueue.c:3340 [inline] worker_thread+0x6c8/0xf10 kernel/workqueue.c:3421 kthread+0x3c5/0x780 kernel/kthread.c:463 ret_from_fork+0x983/0xb10 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246

Allocated by task 5932: kasan_save_stack+0x33/0x60 mm/kasan/common.c:56 kasan_save_track+0x14/0x30 mm/kasan/common.c:77 poison_kmalloc_redzone mm/kasan/common.c:400 [inline] __kasan_kmalloc+0xaa/0xb0 mm/kasan/common.c:417 kmalloc_noprof include/linux/slab.h:957 [inline] kzalloc_noprof include/linux/slab.h:1094 [inline] __hci_conn_add+0xf8/0x1c70 net/bluetooth/hci_conn.c:963 hci_conn_add_unset+0x76/0x100 net/bluetooth/hci_conn.c:1084 le_conn_complete_evt+0x639/0x1f20 net/bluetooth/hci_event.c:5714 hci_le_enh_conn_complete_evt+0x23d/0x380 net/bluetooth/hci_event.c:5861 hci_le_meta_evt+0x357/0x5e0 net/bluetooth/hci_event.c:7408 hci_event_func net/bluetooth/hci_event.c:7716 [inline] hci_event_packet+0x685/0x11c0 net/bluetooth/hci_event.c:7773 hci_rx_work+0x2c9/0xeb0 net/bluetooth/hci_core.c:4076 process_one_work+0x9ba/0x1b20 kernel/workqueue.c:3257 process_scheduled_works kernel/workqueue.c:3340 [inline] worker_thread+0x6c8/0xf10 kernel/workqueue.c:3421 kthread+0x3c5/0x780 kernel/kthread.c:463 ret_from_fork+0x983/0xb10 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246

Freed by task 5932: kasan_save_stack+0x33/0x60 mm/kasan/common.c:56 kasan_save_track+0x14/0x30 mm/kasan/common.c:77 __kasan_save_free_info+0x3b/0x60 mm/kasan/generic.c:587 kasan_save_free_info mm/kasan/kasan.h:406 [inline] poison_slab_object mm/kasan/common.c:252 [inline] __kasan_slab_free+0x5f/0x80 mm/kasan/common.c:284 kasan_slab_free include/linux/kasan.h:234 [inline] slab_free_hook mm/slub.c:2540 [inline] slab_free mm/slub.c:6663 [inline] kfree+0x2f8/0x6e0 mm/slub.c:6871 device_release+0xa4/0x240 drivers/base/core.c:2565 kobject_cleanup lib/kobject.c:689 [inline] kobject_release lib/kobject.c:720 [inline] kref_put include/linux/kref.h:65 [inline] kobject_put+0x1e7/0x590 lib/kobject. ---truncated---

CVSS v3
8.8
EG Score
8.8(medium)
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
13%
KEV
Not listed

Published

May 8, 2026

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

Bluetooth: hci_sync: Fix UAF in le_read_features_complete - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/260dc2be643b4a35b27008490c533613e3e53867
generic

Bluetooth: hci_sync: Fix UAF in le_read_features_complete - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/035c25007c9e698bef3826070ee34bb6d778020c

Vendor Advisories for CVE-2026-43322(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-211.20.1.el10_22026-06-04redhat
linuxKernel @ 6.19.12—osv

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (125 versions)6.19.12-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 28× 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.

Showing the most recent 100 of 243 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 19:31 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCOSV refresh
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 09:37 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:01 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-01 13:54 UTCEPSS rescore
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:46 UTCEPSS rescore
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-23 19:16 UTCEG score recompute
  24. 2026-08-23 19:16 UTCVendor advisory
  25. 2026-08-23 19:16 UTCGHSA enrichment
Show 75 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-17 11:56 UTCEG score recompute
  8. 2026-08-17 11:56 UTCVendor advisory
  9. 2026-08-17 11:56 UTCGHSA enrichment
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 04:38 UTCEG score recompute
  12. 2026-08-16 04:38 UTCVendor advisory
  13. 2026-08-16 04:38 UTCGHSA enrichment
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-14 16:08 UTCVendor advisory
  17. 2026-08-14 16:08 UTCGHSA enrichment
  18. 2026-08-14 03:11 UTCEG score recompute
  19. 2026-08-14 03:11 UTCVendor advisory
  20. 2026-08-14 03:11 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 06:00 UTCVendor advisory
  23. 2026-08-13 06:00 UTCGHSA enrichment
  24. 2026-08-12 16:49 UTCEG score recompute
  25. 2026-08-12 16:49 UTCVendor advisory
  26. 2026-08-12 16:49 UTCGHSA enrichment
  27. 2026-08-12 13:51 UTCEPSS rescore
  28. 2026-08-11 15:53 UTCEG score recompute
  29. 2026-08-11 15:53 UTCVendor advisory
  30. 2026-08-11 15:53 UTCGHSA enrichment
  31. 2026-08-11 13:43 UTCEPSS rescore
  32. 2026-08-11 01:19 UTCEG score recompute
  33. 2026-08-11 01:19 UTCVendor advisory
  34. 2026-08-11 01:19 UTCGHSA enrichment
  35. 2026-08-11 00:00 UTCEPSS rescore
  36. 2026-08-10 04:19 UTCVendor advisory
  37. 2026-08-10 04:19 UTCGHSA enrichment
  38. 2026-08-09 15:23 UTCEG score recompute
  39. 2026-08-09 15:23 UTCVendor advisory
  40. 2026-08-09 15:23 UTCGHSA enrichment
  41. 2026-08-09 13:46 UTCEPSS rescore
  42. 2026-08-09 02:26 UTCEG score recompute
  43. 2026-08-09 02:26 UTCVendor advisory
  44. 2026-08-09 02:26 UTCGHSA enrichment
  45. 2026-08-08 16:37 UTCEPSS rescore
  46. 2026-08-08 10:51 UTCVendor advisory
  47. 2026-08-08 10:51 UTCGHSA enrichment
  48. 2026-08-07 21:46 UTCEG score recompute
  49. 2026-08-07 21:46 UTCVendor advisory
  50. 2026-08-07 21:46 UTCGHSA enrichment
  51. 2026-08-07 08:49 UTCVendor advisory
  52. 2026-08-07 08:49 UTCGHSA enrichment
  53. 2026-08-06 16:52 UTCEG score recompute
  54. 2026-08-06 16:52 UTCVendor advisory
  55. 2026-08-06 16:52 UTCGHSA enrichment
  56. 2026-08-06 13:46 UTCEPSS rescore
  57. 2026-08-06 02:47 UTCEG score recompute
  58. 2026-08-06 02:47 UTCVendor advisory
  59. 2026-08-06 02:47 UTCGHSA enrichment
  60. 2026-08-05 19:17 UTCEPSS rescore
  61. 2026-08-05 13:50 UTCEG score recompute
  62. 2026-08-05 13:50 UTCVendor advisory
  63. 2026-08-05 13:50 UTCGHSA enrichment
  64. 2026-08-04 15:10 UTCEPSS rescore
  65. 2026-08-04 10:38 UTCEPSS rescore
  66. 2026-08-03 19:33 UTCEG score recompute
  67. 2026-08-03 19:33 UTCVendor advisory
  68. 2026-08-03 19:33 UTCGHSA enrichment
  69. 2026-08-03 10:36 UTCEPSS rescore
  70. 2026-08-02 16:06 UTCVendor advisory
  71. 2026-08-02 16:06 UTCGHSA enrichment
  72. 2026-08-02 03:07 UTCEG score recompute
  73. 2026-08-02 03:07 UTCVendor advisory
  74. 2026-08-02 03:07 UTCGHSA enrichment
  75. 2026-08-02 02:27 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43322?
CVE-2026-43322 is a high vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hcisync: Fix UAF in lereadfeaturescomplete This fixes the following backtrace caused by hci_conn being freed before lereadfeatures_complete but after hcilereadremotefeaturessync so hciconndel -> hcicmdsyncdequeue is not…
When was CVE-2026-43322 disclosed?
CVE-2026-43322 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43322 actively exploited?
CVE-2026-43322 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 87.3% of all scored CVEs.
What is the CVSS score of CVE-2026-43322?
CVE-2026-43322 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-43322?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43322, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-43322?

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

Start Free Scan →Browse All CVEs