# CVE-2022-49193: linux: In the Linux kernel, the following vulnerability has been resolved:  ice: fix 'scheduling while atomic' on aux critic...

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.

- Web page: https://patchblox.com/security/cve/CVE-2022-49193
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: 0.0027
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Feb 26, 2025

## Description

In the Linux kernel, the following vulnerability has been resolved:  ice: fix 'scheduling while atomic' on aux critical err interrupt  There's 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]  <IRQ> [ 2101.065252]  dump_stack+0x41/0x60 [ 2101.068587]  __schedule_bug.cold.100+0x4c/0x58 [ 2101.073060]  __schedule+0x6a4/0x830 [ 2101.076570]  schedule+0x35/0xa0 [ 2101.079727]  schedule_preempt_disabled+0xa/0x10 [ 2101.084284]  __mutex_lock.isra.7+0x310/0x420 [ 2101.088580]  ? ice_misc_intr+0x201/0x2e0 [ice] [ 2101.093078]  ice_send_event_to_aux+0x25/0x70 [ice] [ 2101.097921]  ice_misc_intr+0x220/0x2e0 [ice] [ 2101.102232]  __handle_irq_event_percpu+0x40/0x180 [ 2101.106965]  handle_irq_event_percpu+0x30/0x80 [ 2101.111434]  handle_irq_event+0x36/0x53 [ 2101.115292]  handle_edge_irq+0x82/0x190 [ 2101.119148]  handle_irq+0x1c/0x30 [ 2101.122480]  do_IRQ+0x49/0xd0 [ 2101.125465]  common_interrupt+0xf/0xf [ 2101.129146]  </IRQ> ...  As Andrew correctly mentioned previously[0], the following call ladder happens:  ice_misc_intr() <- hardirq   ice_send_event_to_aux()     device_lock()       mutex_lock()         might_sleep()           might_resched() <- 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't worth explicit synchronizing (and they're even in the same byte [31:24]).  [0] https://lore.kernel.org/all/YeSRUVmrdmlUXHDn@lunn.ch

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 12.15 (bookworm) | 5.17.3-1 | [DEBIAN-CVE-2022-49193](https://patchblox.com/security/data/fix/linux/debian-cve-2022-49193.md) | Feb 26, 2025 |
| Linux | linux Debian 13.5 (trixie) | 5.17.3-1 | [DEBIAN-CVE-2022-49193](https://patchblox.com/security/data/fix/linux/debian-cve-2022-49193.md) | Feb 26, 2025 |
| Linux | linux Debian 14 | 5.17.3-1 | [DEBIAN-CVE-2022-49193](https://patchblox.com/security/data/fix/linux/debian-cve-2022-49193.md) | Feb 26, 2025 |

---

Data as of 2026-11-08T13:06:02Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.