irqchip/gic-v4: Don't allow a VMOVP on a dying VPE
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.228, 5.15.169, 6.1.114, 6.11.5, 6.6.58
- CVEs
- CVE-2024-50192
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 19:46 UTC · Revision 1
Source evidence
irqchip/gic-v4: Don't allow a VMOVP on a dying VPE
core-osv · Original sourcePublished 8 Nov 2024, 05:54 UTC
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.
osv:CVE-2024-50192
Kernel
Fixed versions: 5.10.228, 5.15.169, 6.1.114, 6.6.58, 6.11.5
Complete source record
{
"id": "c9eef01f4f0804706eb1066294a370817a650f6dd80e0c8409a2e4be2aa56a67",
"url": "https://osv.dev/vulnerability/CVE-2024-50192",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "irqchip/gic-v4: Don't allow a VMOVP on a dying VPE",
"summary": "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.",
"evidence": "osv:CVE-2024-50192",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.10.228",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.169",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.114",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.58",
"evidence": "/affected/1/ranges"
},
{
"value": "6.11.5",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "CVE-2024-50192",
"aliases": [
"CVE-2024-50192"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "64edfaa9a2342a3ce34f8cb982c2c2df84db4de3"
},
{
"fixed": "b7d7b7fc876f836f40bf48a87e07ea18756ba196"
},
{
"fixed": "755b9532c885b8761fb135fedcd705e21e61cccb"
},
{
"fixed": "64b12b061c5488e2d69e67c4eaae5da64fd30bfe"
},
{
"fixed": "01282ab5182f85e42234df2ff42f0ce790f465ff"
},
{
"fixed": "d960505a869e66184fff97fb334980a5b797c7c6"
},
{
"fixed": "1442ee0011983f0c5c4b92380e6853afb513841a"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-50192.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.6.0"
},
{
"fixed": "5.10.228"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.169"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.114"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.58"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.11.5"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-50192.json"
}
}
],
"modified": "2026-10-28T02:30:23.176924414Z",
"provider": "osv",
"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",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/50xxx/CVE-2024-50192.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-50192",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/50xxx/CVE-2024-50192.json"
}
},
"related_cves": [
{
"value": "CVE-2024-50192",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 489358,
"published_at": "2024-11-08T05:54:07.535+00:00"
}