In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v4: Don't allow a VMOVP on a dying VPE Kunkun Jiang reported that there is a small window of opportunity for userspace to force a change of affinity for a VPE while the VPE has already been unmapped, but the corresponding doorbell interrupt still visible in /proc/irq/. Plug the race by checking the value of vmapp_count, which tracks whether the VPE is mapped ot not, and returning an error in this case. This involves making vmapp_count common to both GICv4.1 and its v4.0 ancestor.
Upstream advisory: https://git.kernel.org/pub/scm/linux/security/vulns.git/tree/cve/published/2024/.CVE-2024-50192mbox
Correct URL for upstream advisory: https://git.kernel.org/pub/scm/linux/security/vulns.git/tree/cve/published/2024/CVE-2024-50192.mbox
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:10944 https://access.redhat.com/errata/RHSA-2024:10944
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:10943 https://access.redhat.com/errata/RHSA-2024:10943
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:11486 https://access.redhat.com/errata/RHSA-2024:11486
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.4 Extended Update Support Via RHSA-2025:3935 https://access.redhat.com/errata/RHSA-2025:3935