What’s Vulnerable › Vulnerabilities

CVE-2024-50192: irqchip/gic-v4: Don't allow a VMOVP on a dying VPE

• Severity: medium (CVSS 4.7 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.2% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2024-11-08 · updated 2026-06-17

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.

Affected products

• Linux kernel: from 5.6 before 5.10.228; from 5.11 before 5.15.169; from 5.16 before 6.1.114; from 6.2 before 6.6.58; from 6.7 before 6.11.5; 6.12-rc1, 6.12-rc2, 6.12-rc3 — fixed in 5.10.228, 5.15.169, 6.1.114, 6.11.5, 6.6.58

How to fix

Upgrade to a fixed version: Linux kernel 5.10.228, 5.15.169, 6.1.114, 6.11.5. Check the vendor advisory for mitigations.

References

• https://git.kernel.org/stable/c/01282ab5182f85e42234df2ff42f0ce790f465ff
• https://git.kernel.org/stable/c/1442ee0011983f0c5c4b92380e6853afb513841a
• https://git.kernel.org/stable/c/64b12b061c5488e2d69e67c4eaae5da64fd30bfe
• https://git.kernel.org/stable/c/755b9532c885b8761fb135fedcd705e21e61cccb
• https://git.kernel.org/stable/c/b7d7b7fc876f836f40bf48a87e07ea18756ba196
• https://git.kernel.org/stable/c/d960505a869e66184fff97fb334980a5b797c7c6
• https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
• https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html

Get alerted when CVE-2024-50192 or the next vulnerability affects your stack