{"id":"DEBIAN-CVE-2024-53195","details":"In the Linux kernel, the following vulnerability has been resolved:  KVM: arm64: Get rid of userspace_irqchip_in_use  Improper use of userspace_irqchip_in_use led to syzbot hitting the following WARN_ON() in kvm_timer_update_irq():  WARNING: CPU: 0 PID: 3281 at arch/arm64/kvm/arch_timer.c:459 kvm_timer_update_irq+0x21c/0x394 Call trace:   kvm_timer_update_irq+0x21c/0x394 arch/arm64/kvm/arch_timer.c:459   kvm_timer_vcpu_reset+0x158/0x684 arch/arm64/kvm/arch_timer.c:968   kvm_reset_vcpu+0x3b4/0x560 arch/arm64/kvm/reset.c:264   kvm_vcpu_set_target arch/arm64/kvm/arm.c:1553 [inline]   kvm_arch_vcpu_ioctl_vcpu_init arch/arm64/kvm/arm.c:1573 [inline]   kvm_arch_vcpu_ioctl+0x112c/0x1b3c arch/arm64/kvm/arm.c:1695   kvm_vcpu_ioctl+0x4ec/0xf74 virt/kvm/kvm_main.c:4658   vfs_ioctl fs/ioctl.c:51 [inline]   __do_sys_ioctl fs/ioctl.c:907 [inline]   __se_sys_ioctl fs/ioctl.c:893 [inline]   __arm64_sys_ioctl+0x108/0x184 fs/ioctl.c:893   __invoke_syscall arch/arm64/kernel/syscall.c:35 [inline]   invoke_syscall+0x78/0x1b8 arch/arm64/kernel/syscall.c:49   el0_svc_common+0xe8/0x1b0 arch/arm64/kernel/syscall.c:132   do_el0_svc+0x40/0x50 arch/arm64/kernel/syscall.c:151   el0_svc+0x54/0x14c arch/arm64/kernel/entry-common.c:712   el0t_64_sync_handler+0x84/0xfc arch/arm64/kernel/entry-common.c:730   el0t_64_sync+0x190/0x194 arch/arm64/kernel/entry.S:598  The following sequence led to the scenario:  - Userspace creates a VM and a vCPU.  - The vCPU is initialized with KVM_ARM_VCPU_PMU_V3 during    KVM_ARM_VCPU_INIT.  - Without any other setup, such as vGIC or vPMU, userspace issues    KVM_RUN on the vCPU. Since the vPMU is requested, but not setup,    kvm_arm_pmu_v3_enable() fails in kvm_arch_vcpu_run_pid_change().    As a result, KVM_RUN returns after enabling the timer, but before    incrementing 'userspace_irqchip_in_use':    kvm_arch_vcpu_run_pid_change()        ret = kvm_arm_pmu_v3_enable()            if (!vcpu-\u003earch.pmu.created)                return -EINVAL;        if (ret)            return ret;        [...]        if (!irqchip_in_kernel(kvm))            static_branch_inc(&userspace_irqchip_in_use);  - Userspace ignores the error and issues KVM_ARM_VCPU_INIT again.    Since the timer is already enabled, control moves through the    following flow, ultimately hitting the WARN_ON():    kvm_timer_vcpu_reset()        if (timer-\u003eenabled)           kvm_timer_update_irq()               if (!userspace_irqchip())                   ret = kvm_vgic_inject_irq()                       ret = vgic_lazy_init()                           if (unlikely(!vgic_initialized(kvm)))                               if (kvm-\u003earch.vgic.vgic_model !=                                   KVM_DEV_TYPE_ARM_VGIC_V2)                                       return -EBUSY;                   WARN_ON(ret);  Theoretically, since userspace_irqchip_in_use's functionality can be simply replaced by '!irqchip_in_kernel()', get rid of the static key to avoid the mismanagement, which also helps with the syzbot issue.","modified":"2026-11-15T18:00:45.938286865Z","published":"2024-12-27T14:15:27.137Z","upstream":["CVE-2024-53195"],"references":[{"type":"ADVISORY","url":"https://security-tracker.debian.org/tracker/CVE-2024-53195"}],"affected":[{"package":{"name":"linux","ecosystem":"Debian:12","purl":"pkg:deb/debian/linux?arch=source&distro=bookworm"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.192-1"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","6.1.112-1","6.1.115-1","6.1.119-1","6.1.123-1","6.1.124-1","6.1.128-1","6.1.129-1","6.1.133-1","6.1.135-1","6.1.137-1","6.1.139-1","6.1.140-1","6.1.147-1","6.1.148-1","6.1.153-1","6.1.158-1","6.1.159-1","6.1.162-1","6.1.164-1","6.1.170-1","6.1.170-2","6.1.170-3","6.1.172-1","6.1.174-1","6.1.176-1","6.1.177-1","6.1.180-1","6.1.187-1","6.1.190-1","6.1.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1","6.1.82-1","6.1.85-1","6.1.90-1","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1","6.1.99-1"],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2024-53195.json"}},{"package":{"name":"linux","ecosystem":"Debian:13","purl":"pkg:deb/debian/linux?arch=source&distro=trixie"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.3-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2024-53195.json"}},{"package":{"name":"linux","ecosystem":"Debian:14","purl":"pkg:deb/debian/linux?arch=source&distro=forky"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.12.3-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2024-53195.json"}}],"schema_version":"1.9.2","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"}]}