CVE-2024-50192
"GICv4: Affinity Changing Vulnerability in irqchip"
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.
INFO
Published Date :
Nov. 8, 2024, 6:15 a.m.
Last Modified :
Nov. 29, 2024, 7 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
3.6
Exploitability Score :
1.0
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-50192.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-50192 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-50192 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Nov. 29, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H Added CWE NIST NVD-CWE-noinfo Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.6 up to (excluding) 5.10.228 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.169 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.114 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.58 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.11.5 *cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.12:rc3:*:*:*:*:*:* Changed Reference Type https://git.kernel.org/stable/c/01282ab5182f85e42234df2ff42f0ce790f465ff No Types Assigned https://git.kernel.org/stable/c/01282ab5182f85e42234df2ff42f0ce790f465ff Patch Changed Reference Type https://git.kernel.org/stable/c/1442ee0011983f0c5c4b92380e6853afb513841a No Types Assigned https://git.kernel.org/stable/c/1442ee0011983f0c5c4b92380e6853afb513841a Patch Changed Reference Type https://git.kernel.org/stable/c/64b12b061c5488e2d69e67c4eaae5da64fd30bfe No Types Assigned https://git.kernel.org/stable/c/64b12b061c5488e2d69e67c4eaae5da64fd30bfe Patch Changed Reference Type https://git.kernel.org/stable/c/755b9532c885b8761fb135fedcd705e21e61cccb No Types Assigned https://git.kernel.org/stable/c/755b9532c885b8761fb135fedcd705e21e61cccb Patch Changed Reference Type https://git.kernel.org/stable/c/b7d7b7fc876f836f40bf48a87e07ea18756ba196 No Types Assigned https://git.kernel.org/stable/c/b7d7b7fc876f836f40bf48a87e07ea18756ba196 Patch Changed Reference Type https://git.kernel.org/stable/c/d960505a869e66184fff97fb334980a5b797c7c6 No Types Assigned https://git.kernel.org/stable/c/d960505a869e66184fff97fb334980a5b797c7c6 Patch -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Nov. 08, 2024
Action Type Old Value New Value Added 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. Added Reference kernel.org https://git.kernel.org/stable/c/b7d7b7fc876f836f40bf48a87e07ea18756ba196 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/755b9532c885b8761fb135fedcd705e21e61cccb [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/64b12b061c5488e2d69e67c4eaae5da64fd30bfe [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/01282ab5182f85e42234df2ff42f0ce790f465ff [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/d960505a869e66184fff97fb334980a5b797c7c6 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/1442ee0011983f0c5c4b92380e6853afb513841a [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-50192 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-50192
weaknesses.