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
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

A fix is available — apply it.

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)
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
3%
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.

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu

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.88-1~bpo12+1 (21 versions)6.12.88-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (133 versions)7.0.7-1—

Weakness Classification(1)

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

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 4× in last 7d / 86× 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 222 total refreshes for this CVE.

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

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 0% probability of exploitation in the next 30 days, which ranks it in the top 97.0% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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