Quick answers
- Is CVE-2026-98292 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-98292 being exploited in the wild.
- How severe is CVE-2026-98292?
- Informational severity, published 6 October 2026.
- Which products and versions are affected?
- Unknown Linux kernel all versions prior to fix (affecting btmtksdio and btmtkuart Bluetooth drivers).
- Is there a fix for CVE-2026-98292?
- Yes: fixed in Fixed in upstream commit 8879e3e0a84a86954c855caceead4867e74a9a27 and available in subsequent stable kernel releases. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-98292 attacked?
- It is attacked from the adjacent network, in an operating system.
- Am I affected by CVE-2026-98292?
- Check whether you run Unknown Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Fixed in upstream commit 8879e3e0a84a86954c855caceead4867e74a9a27 and available in subsequent stable kernel releases
Technical details
The vulnerability exists in btmtksdio.c and btmtkuart.c where WMT event payloads are cast directly to struct pointers and fields accessed without validating the packet is long enough to contain them. The FUNC_CTRL case additionally reads a 2-byte status field without length checking, causing out-of-bounds reads via unchecked buffer access (CWE-125). This requires receipt of a malformed WMT response packet from the Bluetooth device firmware and has been fixed by adding skb_pull_data() validation before field access.
Affected products
- <UNKNOWN> Linux kernel all versions prior to fix (affecting btmtksdio and btmtkuart Bluetooth drivers)
Timeline
- 2026-09-15: disclosed
- 2026-09-25: patched