CVE-2026-98292: Bluetooth: btmtksdio, btmtkuart: validate WMT event length before struct access
Bluetooth: btmtksdio, btmtkuart: validate WMT event length before struct access
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ubuntu/linux-hwe-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42~24.04.1 - Upgrade
Upgrade
ubuntu/linux-riscv-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1~24.04.1 - Upgrade
Upgrade
ubuntu/linuxto a version that resolves this vulnerability.Fixed in 7.0.0-42.42 - Upgrade
Upgrade
ubuntu/linux-awsto a version that resolves this vulnerability.Fixed in 7.0.0-1016.17 - Upgrade
Upgrade
ubuntu/linux-gcpto a version that resolves this vulnerability.Fixed in 7.0.0-1016.18 - Upgrade
Upgrade
ubuntu/linux-ibmto a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oem-7.0to a version that resolves this vulnerability.Fixed in 7.0.0-1017.17 - Upgrade
Upgrade
ubuntu/linux-oracleto a version that resolves this vulnerability.Fixed in 7.0.0-1015.16 - Upgrade
Upgrade
ubuntu/linux-riscvto a version that resolves this vulnerability.Fixed in 7.0.0-42.42.1
Event History
Frequently Asked Questions
Which Linux kernel components are affected?
The issue is in the btmtksdio and btmtkuart Bluetooth drivers, which process WMT events received from firmware. The fix was verified without regression on MT7920, MT7921, MT7922, and MT7925 hardware.
What is required to trigger the out-of-bounds read?
The affected driver must receive a short or malformed WMT event from Bluetooth firmware. In particular, the vulnerable paths access WMT header fields, and in the FUNC_CTRL case a status field, without first confirming that the received SKB contains enough data.