CVE-2026-46140

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: 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: btmtk: validate WMT event SKB length before struct access

btmtk_usb_hci_wmt_sync() casts the WMT event response SKB data to struct btmtk_hci_wmt_evt (7 bytes) and struct btmtk_hci_wmt_evt_funcc (9 bytes) without first checking that the SKB contains enough data. A short firmware response causes out-of-bounds reads from SKB tailroom.

Use skb_pull_data() to validate and advance past the base WMT event header. For the FUNC_CTRL case, pull the additional status field bytes before accessing them.

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

Published

May 28, 2026

Last Modified

July 4, 2026

Advisory Details (4)

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

Bluetooth: btmtk: validate WMT event SKB length before struct access - kernel/git/stable/linux.git - Linux kernel stable tree

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

Bluetooth: btmtk: validate WMT event SKB length before struct access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/70d37a8b9229e394cc17ddad47e90b81d80fcd09
generic

Bluetooth: btmtk: validate WMT event SKB length before struct access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/634a4408c0615c523cf7531790f4f14a422b9206
generic

Bluetooth: btmtk: validate WMT event SKB length before struct access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/624fb79dadc1b65757986a9d0fdde5c0cf3fe179

Vendor Advisories for CVE-2026-46140(2)

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 9× in last 7d / 69× 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 107 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-46140?
CVE-2026-46140 is a high vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btmtk: validate WMT event SKB length before struct access btmtkusbhciwmtsync() casts the WMT event response SKB data to struct btmtkhciwmtevt (7 bytes) and struct btmtkhciwmtevt_funcc (9 bytes) without first checking…
When was CVE-2026-46140 disclosed?
CVE-2026-46140 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on July 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46140 actively exploited?
CVE-2026-46140 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-46140?
CVE-2026-46140 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-46140?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46140, 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-46140

Explore →

Is Your Infrastructure Affected by CVE-2026-46140?

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

Start Free Scan →Browse All CVEs