CVE-2024-50192

Source
https://cve.org/CVERecord?id=CVE-2024-50192
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-50192.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2024-50192
Downstream
Related
Published
2024-11-08T05:54:07.535Z
Modified
2026-03-20T12:39:37.164564Z
Severity
  • 4.7 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
irqchip/gic-v4: Don't allow a VMOVP on a dying VPE
Details

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.

Database specific
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/50xxx/CVE-2024-50192.json",
    "cna_assigner": "Linux"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
64edfaa9a2342a3ce34f8cb982c2c2df84db4de3
Fixed
b7d7b7fc876f836f40bf48a87e07ea18756ba196
Fixed
755b9532c885b8761fb135fedcd705e21e61cccb
Fixed
64b12b061c5488e2d69e67c4eaae5da64fd30bfe
Fixed
01282ab5182f85e42234df2ff42f0ce790f465ff
Fixed
d960505a869e66184fff97fb334980a5b797c7c6
Fixed
1442ee0011983f0c5c4b92380e6853afb513841a

Database specific

source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2024-50192.json"