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

Published Nov 8, 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 vmappcount, which tracks whether the VPE is mapped ot not, and returning an error in this case.

This involves making vmappcount common to both GICv4.1 and its v4.0 ancestor.

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

14 affected componentsFixes available
Linux Linux kernel>=5.6<5.10.228
Linux Linux kernel>=5.11<5.15.169
Linux Linux kernel>=5.16<6.1.114
Linux Linux kernel>=6.2<6.6.58
Linux Linux kernel>=6.7<6.11.5
Linux Linux kernel=6.12-rc1
Linux Linux kernel=6.12-rc2
Linux Linux kernel=6.12-rc3
debian/linux<=5.10.223-1
5.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
debian/linux-6.1
6.1.129-1~deb11u1
Microsoft cbl2 kernel 5.15.167.1-2<5.15.173.1-1
5.15.173.1-1
Microsoft azl3 kernel 6.6.57.1-7<6.6.64.2-1
6.6.64.2-1
Microsoft azl3 kernel 6.6.64.2-1<6.6.64.2-1
6.6.64.2-1
Microsoft cbl2 kernel 5.15.173.1-1<5.15.173.1-1
5.15.173.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
  2. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.129-1~deb11u1
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 5.15.173.1-1
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.64.2-1

Event History

Nov 8, 2024
CVE Published
via MITRE·05:54 AM
Data Sourced
via MITRE·05:54 AM
Description
Data Sourced
via NVD·06:15 AM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Red Hat·01:48 PM
DescriptionSeverityAffected Software
Dec 12, 2024
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:00 AM
Affected Software
Updated
via Microsoft·08:00 AM
Affected Software
Updated
via Microsoft·08:00 AM
SeverityAffected Software
Updated
via Microsoft·08:00 AM
Description
Feb 20, 2025
Data Sourced
via Launchpad·12:45 AM
Description
May 3, 2025
Data Sourced
via Ubuntu·01:01 AM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

5

Who reported the CVE-2024-50192 vulnerability?

CVE-2024-50192 was reported by Kunkun Jiang.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203