{
  "cveId": "CVE-2022-49200",
  "url": "https://patchblox.com/security/cve/CVE-2022-49200",
  "summary": "CVE-2022-49200 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-49200, released February 26, 2025. It is not reported as exploited. Patch Radar priority: Routine.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  Bluetooth: btmtksdio: Fix kernel oops in btmtksd...",
  "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\u002B0x28/0x54 [   14.339139]  process_sdio_pending_irqs\u002B0x68/0x1a0 [   14.339144]  sdio_irq_work\u002B0x40/0x70 [   14.339154]  process_one_work\u002B0x184/0x39c [   14.339160]  worker_thread\u002B0x228/0x3e8 [   14.339168]  kthread\u002B0x148/0x3ac [   14.339176]  ret_from_fork\u002B0x10/0x30  That happened because hdev-\u003Epower_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-\u003Ereq_workqueue, \u0026hdev-\u003Epower_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.",
  "published": "2025-02-26T07:00:57Z",
  "severity": "medium",
  "cvss": 5.5,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
  "epss": 0.00269,
  "epssPercentile": 0.19231,
  "priority": "Routine",
  "priorityTier": 4,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "5.17.3-1",
      "fix": "DEBIAN-CVE-2022-49200",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49200",
      "released": "2025-02-26T07:00:57Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "5.17.3-1",
      "fix": "DEBIAN-CVE-2022-49200",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49200",
      "released": "2025-02-26T07:00:57Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "5.17.3-1",
      "fix": "DEBIAN-CVE-2022-49200",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49200",
      "released": "2025-02-26T07:00:57Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T06:59:42Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}