CVE-2026-43020

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

Bluetooth: MGMT: validate LTK enc_size on load

Load Long Term Keys stores the user-provided enc_size and later uses it to size fixed-size stack operations when replying to LE LTK requests. An enc_size larger than the 16-byte key buffer can therefore overflow the reply stack buffer.

Reject oversized enc_size values while validating the management LTK record so invalid keys never reach the stored key state.

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

Published

May 1, 2026

Last Modified

May 8, 2026

Advisory Details (8)

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

Bluetooth: MGMT: validate LTK enc_size on load - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: MGMT: validate LTK enc_size on load - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: MGMT: validate LTK enc_size on load - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: MGMT: validate LTK enc_size on load - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/82f342b3b006ca1d65f4890c05f2ec32fcb808b6
generic

Bluetooth: MGMT: validate LTK enc_size on load - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50fb64defa72a3fecd0af1ca7c6b47b5c5c2b257
generic

Bluetooth: MGMT: validate LTK enc_size on load - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/40ba329e8b4cd2fb11b0caf5e6a543ceaebb6009
generic

Bluetooth: MGMT: validate LTK enc_size on load - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/257cdb960d8ff6d60bb6461b03c814b6cf0c9e64
generic

Bluetooth: MGMT: validate LTK enc_size on load - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0f37d1e65c6d71ad94ccfb5c602163c525db789d

Vendor Advisories for CVE-2026-43020(4)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:4.18.0-553.126.1.el8_102026-05-28redhat
redhatkernel-0:5.14.0-687.12.1.el9_82026-05-28redhat
redhatkernel-0:6.12.0-211.18.1.el10_22026-05-28redhat
redhatkernel-rt-0:4.18.0-553.126.1.rt7.467.el8_102026-05-28redhat
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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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 126 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-43020?
CVE-2026-43020 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: validate LTK enc_size on load Load Long Term Keys stores the user-provided enc_size and later uses it to size fixed-size stack operations when replying to LE LTK requests. An enc_size larger than the 16-byte key…
When was CVE-2026-43020 disclosed?
CVE-2026-43020 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43020 actively exploited?
CVE-2026-43020 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43020?
CVE-2026-43020 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43020?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43020, 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-43020

Explore →

Is Your Infrastructure Affected by CVE-2026-43020?

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

Start Free Scan →Browse All CVEs