Kernel crash via uninitialized Bluetooth driver data
Published Feb 26, 2025 · Updated May 11, 2026
Use of an uninitialized resource in the Linux kernel Bluetooth SDIO driver allows local users to trigger a kernel crash during device power-on. The btmtksdio_probe path registers the HCI device before calling sdio_set_drvdata, so high-priority power-on work can enable an interrupt that makes btmtksdio_interrupt dereference unset driver data. Exploitation requires a system using the MediaTek Bluetooth SDIO driver and access sufficient to initiate device power-on; the reported consequence is a kernel oops and service interruption.
Summary
What happened
Use of an uninitialized resource in the Linux kernel Bluetooth SDIO driver allows local users to trigger a kernel crash during device power-on. The btmtksdio_probe path registers the HCI device before calling sdio_set_drvdata, so high-priority power-on work can enable an interrupt that makes btmtksdio_interrupt dereference unset driver data. Exploitation requires a system using the MediaTek Bluetooth SDIO driver and access sufficient to initiate device power-on; the reported consequence is a kernel oops and service interruption.
The record
- CVE
- CVE-2022-49200
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-908
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.2
- Affected versionversion=9aebfd4a2200ab8075e44379c758bccefdc589bb <4d3d1f2c35a19988d3c5f0ee86038b525e830840
- Affected versionversion=9aebfd4a2200ab8075e44379c758bccefdc589bb <6d7be5afbb41c918d2f12f857f8c7efa50500be2
- Affected versionversion=9aebfd4a2200ab8075e44379c758bccefdc589bb <70a6cf749d9ff9f463490248322e5343199bc267
- Affected versionversion=9aebfd4a2200ab8075e44379c758bccefdc589bb <770a97d3f34b801de1b04737b43e02c55118c41a
- Affected versionversion=9aebfd4a2200ab8075e44379c758bccefdc589bb <874eca93966a786eace87fa6dfb206c2dd9519b1
- Affected versionversion=9aebfd4a2200ab8075e44379c758bccefdc589bb <b062a0b9c1dc1ff63094337dccfe1568d5b62023
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo