CVE-2024-50192: irqchip/gic-v4: Don't allow a VMOVP on a dying VPE
First published: Fri Nov 08 2024(Updated: )
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.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Linux Kernel | >=5.6<5.10.228 | |
| Linux Kernel | >=5.11<5.15.169 | |
| Linux Kernel | >=5.16<6.1.114 | |
| Linux Kernel | >=6.2<6.6.58 | |
| Linux Kernel | >=6.7<6.11.5 | |
| Linux Kernel | =6.12-rc1 | |
| Linux Kernel | =6.12-rc2 | |
| Linux Kernel | =6.12-rc3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/b7d7b7fc876f836f40bf48a87e07ea18756ba196
- https://git.kernel.org/stable/c/755b9532c885b8761fb135fedcd705e21e61cccb
- https://git.kernel.org/stable/c/64b12b061c5488e2d69e67c4eaae5da64fd30bfe
- https://git.kernel.org/stable/c/01282ab5182f85e42234df2ff42f0ce790f465ff
- https://git.kernel.org/stable/c/d960505a869e66184fff97fb334980a5b797c7c6
- https://git.kernel.org/stable/c/1442ee0011983f0c5c4b92380e6853afb513841a
- https://git.kernel.org/pub/scm/linux/security/vulns.git/tree/cve/published/2024/.CVE-2024-50192mbox
- https://git.kernel.org/pub/scm/linux/security/vulns.git/tree/cve/published/2024/CVE-2024-50192.mbox
- https://access.redhat.com/errata/RHSA-2024:10944
- https://access.redhat.com/errata/RHSA-2024:10943
- https://access.redhat.com/errata/RHSA-2024:11486
- https://bugzilla.redhat.com/show_bug.cgi?id=2324612
Frequently Asked Questions
What is the severity of CVE-2024-50192?
CVE-2024-50192 has been classified with a severity level that indicates a potential security risk related to VMOVP operations on a dying VPE.
How do I fix CVE-2024-50192?
To resolve CVE-2024-50192, update your Linux kernel to a version that includes the patch addressing this vulnerability.
Which versions of the Linux kernel are affected by CVE-2024-50192?
CVE-2024-50192 affects specific versions of the Linux kernel ranging from 5.6 to 6.12-rc3.
What potential impact does CVE-2024-50192 have on system security?
CVE-2024-50192 could allow userspace to improperly change the affinity for a VPE, leading to possible system instability or security breaches.
Who reported the CVE-2024-50192 vulnerability?
CVE-2024-50192 was reported by Kunkun Jiang.
- agent/title
- agent/first-publish-date
- agent/type
- agent/author
- agent/remedy
- agent/softwarecombine
- agent/severity
- agent/description
- agent/event
- agent/references
- collector/mitre-cve
- source/MITRE
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2024-50192
- agent/last-modified-date
- agent/source
- agent/tags
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/linux
- canonical/linux kernel
- version/linux kernel/5.6
- version/linux kernel/5.11
- version/linux kernel/5.16
- version/linux kernel/6.2
- version/linux kernel/6.7
- version/linux kernel/6.12-rc1
- version/linux kernel/6.12-rc2
- version/linux kernel/6.12-rc3