Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 18 days later

    Published

  3. · 18 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-50192, by who scored it
Scored byCVSSScoreVector
CISA-ADPADP (enrichment)3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
NVDNVD · Modified3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.7.

Affected products

  • Linux · Linux

    • affected 64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 – < b7d7b7fc876f836f40bf48a87e07ea18756ba196
    • affected 64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 – < 755b9532c885b8761fb135fedcd705e21e61cccb
    • affected 64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 – < 64b12b061c5488e2d69e67c4eaae5da64fd30bfe
    • affected 64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 – < 01282ab5182f85e42234df2ff42f0ce790f465ff
    • affected 64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 – < d960505a869e66184fff97fb334980a5b797c7c6
    • affected 64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 – < 1442ee0011983f0c5c4b92380e6853afb513841a
  • Linux · Linux

    • affected 5.6
    • unaffected < 5.6
    • unaffected 5.10.228 – ≤ 5.10.*
    • unaffected 5.15.169 – ≤ 5.15.*
    • unaffected 6.1.114 – ≤ 6.1.*
    • unaffected 6.6.58 – ≤ 6.6.*
    • unaffected 6.11.5 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-50192 badge
[![CVE-2024-50192](https://cveledger.app/badge/CVE-2024-50192.svg)](https://cveledger.app/cve/CVE-2024-50192)

Record last updated .