Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-98292 Overview
CVE-2026-98292 is an out-of-bounds read vulnerability in the Linux kernel Bluetooth subsystem. The flaw affects the btmtksdio and btmtkuart MediaTek Bluetooth drivers. Both drivers cast received Wireless Management Transport (WMT) events directly to struct btmtk_hci_wmt_evt without validating the socket buffer (SKB) length. A short or malformed WMT event from firmware causes the drivers to read past the end of the SKB. The FUNC_CTRL path extends the problem by further casting to struct btmtk_hci_wmt_evt_funcc and reading a 2-byte status field, again without a length check. Verified affected hardware includes MediaTek MT7920, MT7921, MT7922, and MT7925 chipsets.
Critical Impact
Malformed firmware-originated WMT events can trigger kernel out-of-bounds reads in MediaTek Bluetooth drivers, potentially leading to information disclosure or kernel instability.
Affected Products
- Linux kernel drivers/bluetooth/btmtksdio.c
- Linux kernel drivers/bluetooth/btmtkuart.c
- Systems using MediaTek MT7920, MT7921, MT7922, and MT7925 Bluetooth chipsets
Discovery Timeline
- 2026-10-06 - CVE-2026-98292 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-98292
Vulnerability Analysis
The vulnerability resides in two MediaTek Bluetooth drivers: btmtksdio.c and btmtkuart.c. Both drivers process incoming WMT events received from the Bluetooth controller firmware. The drivers cast the raw SKB payload directly to struct btmtk_hci_wmt_evt and read the op and flag fields without verifying that the SKB contains enough bytes to hold the structure.
The FUNC_CTRL handler aggravates the issue by performing a secondary cast to struct btmtk_hci_wmt_evt_funcc and reading a 2-byte status field. This second read also lacks a length check. When firmware delivers a short or malformed WMT event, the drivers read memory beyond the valid SKB boundary.
The sibling driver btmtk.c already performs the correct validation using skb_pull_data() before dereferencing header fields. The fix mirrors this safer pattern in both affected drivers.
Root Cause
The root cause is missing input validation on untrusted data received from the Bluetooth controller. The drivers trust that the firmware will always send WMT events of the expected minimum length and perform struct casts without boundary verification. This is a classic out-of-bounds read pattern caused by implicit trust in device-supplied length values.
Attack Vector
Exploitation requires a malicious or malfunctioning Bluetooth controller that emits short or malformed WMT events. The attack surface is local to the host-controller interface. A compromised firmware image, a tampered USB/SDIO/UART Bluetooth module, or firmware fault injection could trigger the condition. Successful triggering reads adjacent kernel memory, which may cause kernel memory disclosure or driver instability depending on surrounding allocations.
No verified public exploit code is available. See the upstream commits for the technical fix: Linux Kernel Commit 5a5cfd84 and Linux Kernel Commit 8879e3e0.
Detection Methods for CVE-2026-98292
Indicators of Compromise
- Unexpected kernel warnings or oopses originating from btmtksdio or btmtkuart modules in dmesg
- KASAN (Kernel Address Sanitizer) reports flagging out-of-bounds reads in WMT event handlers
- Bluetooth subsystem instability or repeated controller resets on MediaTek MT79xx hardware
Detection Strategies
- Enable KASAN on test kernels to surface out-of-bounds reads in the Bluetooth stack during fuzzing or regression testing
- Audit kernel version strings across the fleet to identify systems running unpatched btmtksdio or btmtkuart drivers
- Monitor kernel ring buffer logs for abnormal WMT event processing errors on MediaTek Bluetooth chipsets
Monitoring Recommendations
- Centralize kernel log collection and alert on crashes referencing btmtk_hci_wmt_evt or FUNC_CTRL handlers
- Track Bluetooth controller firmware versions on managed endpoints to detect downgrades or tampering
- Correlate Bluetooth driver faults with physical access events to identify potential hardware-level attack attempts
How to Mitigate CVE-2026-98292
Immediate Actions Required
- Apply the upstream Linux kernel patches referenced in the commits for btmtksdio.c and btmtkuart.c
- Update to a stable kernel release that includes commits 5a5cfd84 and 8879e3e0
- On systems where Bluetooth is not required, disable the btmtksdio and btmtkuart modules via module blacklist
Patch Information
The fix mirrors the validated pattern already present in btmtk.c. It uses skb_pull_data() to validate the base WMT header before dereferencing any fields. For FUNC_CTRL events that arrive in short header-only form, the result is decoded from the header's own flag byte (0 = success, otherwise failure) rather than reading a nonexistent status word. Patches are available in the mainline kernel via commit 5a5cfd84 and commit 8879e3e0.
Workarounds
- Blacklist the btmtksdio and btmtkuart kernel modules on systems that do not require MediaTek Bluetooth functionality
- Physically disable Bluetooth radios on high-risk endpoints until patches are deployed
- Restrict physical access to systems with MediaTek Bluetooth hardware to reduce the risk of malicious controller substitution
# Blacklist the affected MediaTek Bluetooth driver modules
echo "blacklist btmtksdio" | sudo tee /etc/modprobe.d/blacklist-btmtk.conf
echo "blacklist btmtkuart" | sudo tee -a /etc/modprobe.d/blacklist-btmtk.conf
sudo update-initramfs -u
sudo reboot
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

