CVE-2026-43019

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
7.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: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

Bluetooth: hci_conn: fix potential UAF in set_cig_params_sync

hci_conn lookup and field access must be covered by hdev lock in set_cig_params_sync, otherwise it's possible it is freed concurrently.

Take hdev lock to prevent hci_conn from being deleted or modified concurrently. Just RCU lock is not suitable here, as we also want to avoid "tearing" in the configuration.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 1, 2026

Last Modified

August 5, 2026

Advisory Details (4)

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

Bluetooth: hci_conn: fix potential UAF in set_cig_params_sync - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: hci_conn: fix potential UAF in set_cig_params_sync - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: hci_conn: fix potential UAF in set_cig_params_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7d568fede8eac91161a60b710aa920abe9b0fb9f
generic

Bluetooth: hci_conn: fix potential UAF in set_cig_params_sync - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/66d432e9b45bae7881ffcdb12cd8fd0bf254ef02

Vendor Advisories for CVE-2026-43019(2)

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

Patch Availability(15)

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (122 versions)6.19.12-1

Weakness Classification(1)

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

All Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 5× in last 7d / 73× 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 208 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43019?
CVE-2026-43019 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hciconn: fix potential UAF in setcigparamssync hci_conn lookup and field access must be covered by hdev lock in setcigparams_sync, otherwise it's possible it is freed concurrently. Take hdev lock to prevent hci_conn from…
When was CVE-2026-43019 disclosed?
CVE-2026-43019 was first published in the National Vulnerability Database on May 1, 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-43019 actively exploited?
CVE-2026-43019 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 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-43019?
CVE-2026-43019 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-43019?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43019, 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-43019

Explore →

Is Your Infrastructure Affected by CVE-2026-43019?

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