{"id":"DEBIAN-CVE-2022-49146","details":"In the Linux kernel, the following vulnerability has been resolved:  virtio: use virtio_device_ready() in virtio_device_restore()  After waking up a suspended VM, the kernel prints the following trace for virtio drivers which do not directly call virtio_device_ready() in the .restore:      PM: suspend exit     irq 22: nobody cared (try booting with the \"irqpoll\" option)     Call Trace:      \u003cIRQ\u003e      dump_stack_lvl+0x38/0x49      dump_stack+0x10/0x12      __report_bad_irq+0x3a/0xaf      note_interrupt.cold+0xb/0x60      handle_irq_event+0x71/0x80      handle_fasteoi_irq+0x95/0x1e0      __common_interrupt+0x6b/0x110      common_interrupt+0x63/0xe0      asm_common_interrupt+0x1e/0x40      ? __do_softirq+0x75/0x2f3      irq_exit_rcu+0x93/0xe0      sysvec_apic_timer_interrupt+0xac/0xd0      \u003c/IRQ\u003e      \u003cTASK\u003e      asm_sysvec_apic_timer_interrupt+0x12/0x20      arch_cpu_idle+0x12/0x20      default_idle_call+0x39/0xf0      do_idle+0x1b5/0x210      cpu_startup_entry+0x20/0x30      start_secondary+0xf3/0x100      secondary_startup_64_no_verify+0xc3/0xcb      \u003c/TASK\u003e     handlers:     [\u003c000000008f9bac49\u003e] vp_interrupt     [\u003c000000008f9bac49\u003e] vp_interrupt     Disabling IRQ #22  This happens because we don't invoke .enable_cbs callback in virtio_device_restore(). That callback is used by some transports (e.g. virtio-pci) to enable interrupts.  Let's fix it, by calling virtio_device_ready() as we do in virtio_dev_probe(). This function calls .enable_cts callback and sets DRIVER_OK status bit.  This fix also avoids setting DRIVER_OK twice for those drivers that call virtio_device_ready() in the .restore.","modified":"2026-09-01T20:04:52.394661025Z","published":"2025-02-26T07:00:51.793Z","upstream":["CVE-2022-49146"],"references":[{"type":"ADVISORY","url":"https://security-tracker.debian.org/tracker/CVE-2022-49146"}],"affected":[{"package":{"name":"linux","ecosystem":"Debian:12","purl":"pkg:deb/debian/linux?arch=source&distro=bookworm"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.17.3-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2022-49146.json"}},{"package":{"name":"linux","ecosystem":"Debian:13","purl":"pkg:deb/debian/linux?arch=source&distro=trixie"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.17.3-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2022-49146.json"}},{"package":{"name":"linux","ecosystem":"Debian:14","purl":"pkg:deb/debian/linux?arch=source&distro=forky"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.17.3-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2022-49146.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"}]}