CVE-2022-49200 Details
Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: btmtksdio: Fix kernel oops in btmtksdio_interrupt Fix the following kernel oops in btmtksdio_interrrupt [ 14.339134] btmtksdio_interrupt+0x28/0x54 [ 14.339139] process_sdio_pending_irqs+0x68/0x1a0 [ 14.339144] sdio_irq_work+0x40/0x70 [ 14.339154] process_one_work+0x184/0x39c [ 14.339160] worker_thread+0x228/0x3e8 [ 14.339168] kthread+0x148/0x3ac [ 14.339176] ret_from_fork+0x10/0x30 That happened because hdev->power_on is already called before sdio_set_drvdata which btmtksdio_interrupt handler relies on is not properly set up. The details are shown as the below: hci_register_dev would run queue_work(hdev->req_workqueue, &hdev->power_on) as WQ_HIGHPRI workqueue_struct to complete the power-on sequeunce and thus hci_power_on may run before sdio_set_drvdata is done in btmtksdio_probe. The hci_dev_do_open in hci_power_on would initialize the device and enable the interrupt and thus it is possible that btmtksdio_interrupt is being called right before sdio_set_drvdata is filled out. When btmtksdio_interrupt is being called and sdio_set_drvdata is not filled , the kernel oops is going to happen because btmtksdio_interrupt access an uninitialized pointer.
A vulnerability in the Linux kernel's Bluetooth subsystem, specifically within the btmtksdio driver, has been addressed. The issue arose because the interrupt handler, btmtksdio_interrupt, was accessing an uninitialized pointer. This situation occurred when the Bluetooth device was powered on and interrupts were enabled before the driver had fully initialized its data. As a result, the interrupt handler could cause a kernel oops, a type of error that leads to a system crash.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/4d3d1f2c35a19988d3c5f0ee86038b525e830840 | kernel.org | Patch |
| https://git.kernel.org/stable/c/6d7be5afbb41c918d2f12f857f8c7efa50500be2 | kernel.org | Patch |
| https://git.kernel.org/stable/c/70a6cf749d9ff9f463490248322e5343199bc267 | kernel.org | Patch |
| https://git.kernel.org/stable/c/770a97d3f34b801de1b04737b43e02c55118c41a | kernel.org | Patch |
| https://git.kernel.org/stable/c/874eca93966a786eace87fa6dfb206c2dd9519b1 | kernel.org | Patch |
| https://git.kernel.org/stable/c/b062a0b9c1dc1ff63094337dccfe1568d5b62023 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-908 | Use of Uninitialized Resource | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.2, < 5.4.189 >= 5.5, < 5.10.110 >= 5.11, < 5.15.33 >= 5.16, < 5.16.19 >= 5.17, < 5.17.2 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Sep 23, 2025 | Initial Analysis | [email protected] |
| Feb 26, 2025 | New CVE Received | kernel.org |