CVE-2026-43062

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.1EG
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.1Exploit: 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: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp()

l2cap_ecred_reconf_rsp() casts the incoming data to struct l2cap_ecred_conn_rsp (the ECRED *connection* response, 8 bytes with result at offset 6) instead of struct l2cap_ecred_reconf_rsp (2 bytes with result at offset 0).

This causes two problems:

  • The sizeof(*rsp) length check requires 8 bytes instead of the
correct 2, so valid L2CAP_ECRED_RECONF_RSP packets are rejected with -EPROTO.
  • rsp->result reads from offset 6 instead of offset 0, returning
wrong data when the packet is large enough to pass the check.

Fix by using the correct type. Also pass the already byte-swapped result variable to BT_DBG instead of the raw __le16 field.

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

Published

May 5, 2026

Last Modified

May 29, 2026

Advisory Details (8)

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

Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5a1ea296f8589ce8f1e3141b2b123b34ad010e19
generic

Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b94e62caa1dc1198d0d55d97bd710da1dee15d7
generic

Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/21d3ba696918d6373233aac0b9d51fcabdedddc0
generic

Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15145675690cab2de1056e7ed68e59cbd0452529
generic

Bluetooth: L2CAP: Fix type confusion in l2cap_ecred_reconf_rsp() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/111f74547eee8cfedfb854284e80f35c8a491186

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253—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.

Data Freshness Timeline

(refreshed 9× 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.

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

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

Related CVEs(same product)

Frequently asked(5)

What is CVE-2026-43062?
CVE-2026-43062 is a high vulnerability published on May 5, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix type confusion in l2capecredreconf_rsp() l2capecredreconf_rsp() casts the incoming data to struct l2capecredconn_rsp (the ECRED connection response, 8 bytes with result at offset 6) instead of struct…
When was CVE-2026-43062 disclosed?
CVE-2026-43062 was first published in the National Vulnerability Database on May 5, 2026, with the most recent update on May 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43062 actively exploited?
CVE-2026-43062 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 88.0% of all scored CVEs.
What is the CVSS score of CVE-2026-43062?
CVE-2026-43062 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-43062?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43062, 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-43062

Explore →

Is Your Infrastructure Affected by CVE-2026-43062?

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

Start Free Scan →Browse All CVEs