CVE-2026-43059

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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: MGMT: Fix list corruption and UAF in command complete handlers

Commit 302a1f674c00 ("Bluetooth: MGMT: Fix possible UAFs") introduced mgmt_pending_valid(), which not only validates the pending command but also unlinks it from the pending list if it is valid. This change in semantics requires updates to several completion handlers to avoid list corruption and memory safety issues.

This patch addresses two left-over issues from the aforementioned rework:

  • In mgmt_add_adv_patterns_monitor_complete(), mgmt_pending_remove()
is replaced with mgmt_pending_free() in the success path. Since mgmt_pending_valid() already unlinks the command at the beginning of the function, calling mgmt_pending_remove() leads to a double list_del() and subsequent list corruption/kernel panic.
  • In set_mesh_complete(), the use of mgmt_pending_foreach() in the error
path is removed. Since the current command is already unlinked by mgmt_pending_valid(), this foreach loop would incorrectly target other pending mesh commands, potentially freeing them while they are still being processed concurrently (leading to UAFs). The redundant mgmt_cmd_status() is also simplified to use cmd->opcode directly.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
2.4%
KEV
Not listed

Published

May 5, 2026

Last Modified

May 22, 2026

Advisory Details (4)

Auto-updated Jun 4, 2026
No patch confirmed yet.
generic

Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/695b45b2262fcb5e71bed1175aad59c72f92aa78
generic

Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/17f89341cb4281d1da0e2fb0de5406ab7c4e25ef
generic

Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/02023ff760cc104a5d86a82ef5b8dd89098ad78d

Vendor Advisories for CVE-2026-43059(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-43059?
CVE-2026-43059 is a high vulnerability published on May 5, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: Fix list corruption and UAF in command complete handlers Commit 302a1f674c00 ("Bluetooth: MGMT: Fix possible UAFs") introduced mgmtpendingvalid(), which not only validates the pending command but also unlinks it…
When was CVE-2026-43059 disclosed?
CVE-2026-43059 was first published in the National Vulnerability Database on May 5, 2026, with the most recent update on May 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43059 actively exploited?
CVE-2026-43059 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43059?
CVE-2026-43059 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43059?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43059, 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-43059

Explore →

Is Your Infrastructure Affected by CVE-2026-43059?

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