{"id":"CVE-2022-49200","summary":"Bluetooth: btmtksdio: Fix kernel oops in btmtksdio_interrupt","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nBluetooth: btmtksdio: Fix kernel oops in btmtksdio_interrupt\n\nFix the following kernel oops in btmtksdio_interrrupt\n\n[   14.339134]  btmtksdio_interrupt+0x28/0x54\n[   14.339139]  process_sdio_pending_irqs+0x68/0x1a0\n[   14.339144]  sdio_irq_work+0x40/0x70\n[   14.339154]  process_one_work+0x184/0x39c\n[   14.339160]  worker_thread+0x228/0x3e8\n[   14.339168]  kthread+0x148/0x3ac\n[   14.339176]  ret_from_fork+0x10/0x30\n\nThat happened because hdev-\u003epower_on is already called before\nsdio_set_drvdata which btmtksdio_interrupt handler relies on is not\nproperly set up.\n\nThe details are shown as the below: hci_register_dev would run\nqueue_work(hdev-\u003ereq_workqueue, &hdev-\u003epower_on) as WQ_HIGHPRI\nworkqueue_struct to complete the power-on sequeunce and thus hci_power_on\nmay run before sdio_set_drvdata is done in btmtksdio_probe.\n\nThe hci_dev_do_open in hci_power_on would initialize the device and enable\nthe interrupt and thus it is possible that btmtksdio_interrupt is being\ncalled right before sdio_set_drvdata is filled out.\n\nWhen btmtksdio_interrupt is being called and sdio_set_drvdata is not filled\n, the kernel oops is going to happen because btmtksdio_interrupt access an\nuninitialized pointer.","modified":"2026-03-20T12:22:15.269879Z","published":"2025-02-26T01:55:42.758Z","related":["SUSE-SU-2025:1027-1","SUSE-SU-2025:1176-1","SUSE-SU-2025:1183-1","SUSE-SU-2025:1194-1","SUSE-SU-2025:1241-1","SUSE-SU-2025:1263-1"],"database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49200.json"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/4d3d1f2c35a19988d3c5f0ee86038b525e830840"},{"type":"WEB","url":"https://git.kernel.org/stable/c/6d7be5afbb41c918d2f12f857f8c7efa50500be2"},{"type":"WEB","url":"https://git.kernel.org/stable/c/70a6cf749d9ff9f463490248322e5343199bc267"},{"type":"WEB","url":"https://git.kernel.org/stable/c/770a97d3f34b801de1b04737b43e02c55118c41a"},{"type":"WEB","url":"https://git.kernel.org/stable/c/874eca93966a786eace87fa6dfb206c2dd9519b1"},{"type":"WEB","url":"https://git.kernel.org/stable/c/b062a0b9c1dc1ff63094337dccfe1568d5b62023"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49200.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49200"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"9aebfd4a2200ab8075e44379c758bccefdc589bb"},{"fixed":"874eca93966a786eace87fa6dfb206c2dd9519b1"},{"fixed":"70a6cf749d9ff9f463490248322e5343199bc267"},{"fixed":"770a97d3f34b801de1b04737b43e02c55118c41a"},{"fixed":"4d3d1f2c35a19988d3c5f0ee86038b525e830840"},{"fixed":"6d7be5afbb41c918d2f12f857f8c7efa50500be2"},{"fixed":"b062a0b9c1dc1ff63094337dccfe1568d5b62023"}]}],"database_specific":{"source":"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-49200.json"}}],"schema_version":"1.7.5"}