CVE-2022-49200
Bluetooth: btmtksdio: Fix kernel oops in btmtksdio_interrupt
- Published
- Updated
- Reserved
- Assigned by
- Linux
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.
Timeline
ID reserved
By Linux
Published
- 15 months later
· 15 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.27% · top 81% of all CVEs (7 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Weakness
Affected products
- affected 9aebfd4a2200ab8075e44379c758bccefdc589bb – < 874eca93966a786eace87fa6dfb206c2dd9519b1
- affected 9aebfd4a2200ab8075e44379c758bccefdc589bb – < 70a6cf749d9ff9f463490248322e5343199bc267
- affected 9aebfd4a2200ab8075e44379c758bccefdc589bb – < 770a97d3f34b801de1b04737b43e02c55118c41a
- affected 9aebfd4a2200ab8075e44379c758bccefdc589bb – < 4d3d1f2c35a19988d3c5f0ee86038b525e830840
- affected 9aebfd4a2200ab8075e44379c758bccefdc589bb – < 6d7be5afbb41c918d2f12f857f8c7efa50500be2
- affected 9aebfd4a2200ab8075e44379c758bccefdc589bb – < b062a0b9c1dc1ff63094337dccfe1568d5b62023
- affected 5.2
- unaffected < 5.2
- unaffected 5.4.189 – ≤ 5.4.*
- unaffected 5.10.110 – ≤ 5.10.*
- unaffected 5.15.33 – ≤ 5.15.*
- unaffected 5.16.19 – ≤ 5.16.*
- unaffected 5.17.2 – ≤ 5.17.*
- unaffected 5.18 – ≤ *
References (6)
- https://git.kernel.org/stable/c/874eca93966a786eace87fa6dfb206c2dd9519b1 (opens in a new tab)
- https://git.kernel.org/stable/c/70a6cf749d9ff9f463490248322e5343199bc267 (opens in a new tab)
- https://git.kernel.org/stable/c/770a97d3f34b801de1b04737b43e02c55118c41a (opens in a new tab)
- https://git.kernel.org/stable/c/4d3d1f2c35a19988d3c5f0ee86038b525e830840 (opens in a new tab)
- https://git.kernel.org/stable/c/6d7be5afbb41c918d2f12f857f8c7efa50500be2 (opens in a new tab)
- https://git.kernel.org/stable/c/b062a0b9c1dc1ff63094337dccfe1568d5b62023 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://trackcve.app/cve/CVE-2022-49200)Record last updated .