CVE-2024-50192 irqchip/gic-v4: Don't allow a VMOVP on a dying VPE
A race condition in the Linux kernel GICv4 driver allows userspace to trigger an invalid affinity change on a dying VPE, potentially causing a denial of service.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2024-50192?
CVE-2024-50192 is a medium-severity vulnerability in Linux kernel, published on 8 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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.
Which versions are affected by CVE-2024-50192?
It affects 1 product.
Products include Linux kernel.
How do I fix CVE-2024-50192?
Apply the vendor's patch.
Is CVE-2024-50192 being exploited?
There is no known exploitation of CVE-2024-50192 in the wild and no public exploit code.
Other vulnerabilities in Linux kernel
Sources
Also known as AZL-53426, AZL-53712, BELL-CVE-2024-50192, DEBIAN-CVE-2024-50192, GHSA-wr4f-chxr-9pr5, UBUNTU-CVE-2024-50192.