{
  "cveId": "CVE-2022-49193",
  "url": "https://patchblox.com/security/cve/CVE-2022-49193",
  "summary": "CVE-2022-49193 is fixed in linux on 1 platform, first by DEBIAN-CVE-2022-49193, 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:  ice: fix \u0027scheduling while atomic\u0027 on aux critic...",
  "description": "In the Linux kernel, the following vulnerability has been resolved:  ice: fix \u0027scheduling while atomic\u0027 on aux critical err interrupt  There\u0027s a kernel BUG splat on processing aux critical error interrupts in ice_misc_intr():  [ 2100.917085] BUG: scheduling while atomic: swapper/15/0/0x00010000 ... [ 2101.060770] Call Trace: [ 2101.063229]  \u003CIRQ\u003E [ 2101.065252]  dump_stack\u002B0x41/0x60 [ 2101.068587]  __schedule_bug.cold.100\u002B0x4c/0x58 [ 2101.073060]  __schedule\u002B0x6a4/0x830 [ 2101.076570]  schedule\u002B0x35/0xa0 [ 2101.079727]  schedule_preempt_disabled\u002B0xa/0x10 [ 2101.084284]  __mutex_lock.isra.7\u002B0x310/0x420 [ 2101.088580]  ? ice_misc_intr\u002B0x201/0x2e0 [ice] [ 2101.093078]  ice_send_event_to_aux\u002B0x25/0x70 [ice] [ 2101.097921]  ice_misc_intr\u002B0x220/0x2e0 [ice] [ 2101.102232]  __handle_irq_event_percpu\u002B0x40/0x180 [ 2101.106965]  handle_irq_event_percpu\u002B0x30/0x80 [ 2101.111434]  handle_irq_event\u002B0x36/0x53 [ 2101.115292]  handle_edge_irq\u002B0x82/0x190 [ 2101.119148]  handle_irq\u002B0x1c/0x30 [ 2101.122480]  do_IRQ\u002B0x49/0xd0 [ 2101.125465]  common_interrupt\u002B0xf/0xf [ 2101.129146]  \u003C/IRQ\u003E ...  As Andrew correctly mentioned previously[0], the following call ladder happens:  ice_misc_intr() \u003C- hardirq   ice_send_event_to_aux()     device_lock()       mutex_lock()         might_sleep()           might_resched() \u003C- oops  Add a new PF state bit which indicates that an aux critical error occurred and serve it in ice_service_task() in process context. The new ice_pf::oicr_err_reg is read-write in both hardirq and process contexts, but only 3 bits of non-critical data probably aren\u0027t worth explicit synchronizing (and they\u0027re even in the same byte [31:24]).  [0] https://lore.kernel.org/all/YeSRUVmrdmlUXHDn@lunn.ch",
  "published": "2025-02-26T07:00:56Z",
  "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.00268,
  "epssPercentile": 0.19075,
  "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-49193",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49193",
      "released": "2025-02-26T07:00:56Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "5.17.3-1",
      "fix": "DEBIAN-CVE-2022-49193",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49193",
      "released": "2025-02-26T07:00:56Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "5.17.3-1",
      "fix": "DEBIAN-CVE-2022-49193",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2022-49193",
      "released": "2025-02-26T07:00:56Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T13:06:02Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}