CVE-2024-50192medium

CVE-2024-50192: medium-severity vulnerability in Linux

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

Published · Updated

13Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 4.7epss 0.2%
exploitation probability
0.2%top 90% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected products
Linux · Linux
Related CVEs — Linux

In the same product, most dangerous first.

CVE-2024-53197HIGHALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devicesEPSS 4.1%KEVCVE-2026-31431HIGHcrypto: algif_aead - Revert to operating out-of-placeEPSS 3.4%KEVCVE-2024-53104HIGHmedia: uvcvideo: Skip parsing frames of type UVC_VS_UNDEFINED in uvc_parse_formatEPSS 3.4%KEVCVE-2025-39682CRITICALtls: fix handling of zero-length records on the rx_listEPSS 2.9%KEVCVE-2024-36971HIGHnet: fix __dst_negative_advice() raceEPSS 2.7%KEVCVE-2024-53150HIGHALSA: usb-audio: Fix out of bounds reads when finding clock sourcesEPSS 1.4%KEV
References
https://git.kernel.org/stable/c/01282ab5182f85e42234df2ff42f0ce790f465ffhttps://git.kernel.org/stable/c/1442ee0011983f0c5c4b92380e6853afb513841ahttps://git.kernel.org/stable/c/64b12b061c5488e2d69e67c4eaae5da64fd30bfehttps://git.kernel.org/stable/c/755b9532c885b8761fb135fedcd705e21e61cccbhttps://git.kernel.org/stable/c/b7d7b7fc876f836f40bf48a87e07ea18756ba196https://git.kernel.org/stable/c/d960505a869e66184fff97fb334980a5b797c7c6https://lists.debian.org/debian-lts-announce/2025/01/msg00001.htmlhttps://lists.debian.org/debian-lts-announce/2025/03/msg00002.html