Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: Linux Linux 01282ab5182f85e42234df2ff42f0ce790f465ff, 1442ee0011983f0c5c4b92380e6853afb513841a, 64b12b061c5488e2d69e67c4eaae5da64fd30bfe; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1.

Low priority for now. Upgrade to Linux Linux 01282ab5182f85e42234df2ff42f0ce790f465ff, 1442ee0011983f0c5c4b92380e6853afb513841a, 64b12b061c5488e2d69e67c4eaae5da64fd30bfe; azl3 kernel 6.6.57.1-7 on Azure Linux 3.0 6.6.64.2-1; azl3 kernel 6.6.64.2-1 on Azure Linux 3.0 6.6.64.2-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 4.7 · v3.1—No exploit Fix available
Published
Nov 8, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 10th percentile
CWE
—

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
18 / 40 · 4.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-50192

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.6 and later · before 5.10.228
  • linux linux kernel5.11 and later · before 5.15.169
  • linux linux kernel5.16 and later · before 6.1.114
  • linux linux kernel6.2 and later · before 6.6.58
  • linux linux kernel6.7 and later · before 6.11.5
  • linux linux kernel6.12

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.6affected
    • 64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 and later · before b7d7b7fc876f836f40bf48a87e07ea18756ba196affected · git
    • 64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 and later · before 755b9532c885b8761fb135fedcd705e21e61cccbaffected · git
    • 64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 and later · before 64b12b061c5488e2d69e67c4eaae5da64fd30bfeaffected · git
    • 64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 and later · before 01282ab5182f85e42234df2ff42f0ce790f465ffaffected · git
    • 64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 and later · before d960505a869e66184fff97fb334980a5b797c7c6affected · git
    • 64edfaa9a2342a3ce34f8cb982c2c2df84db4de3 and later · before 1442ee0011983f0c5c4b92380e6853afb513841aaffected · git
    • before 5.6not affected · semver
    • 5.10.228 and later · up to and including 5.10.*not affected · semver
    • 5.15.169 and later · up to and including 5.15.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.32.1.el8_104.18.0-553.32.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.32.1.rt7.373.el8_104.18.0-553.32.1.rt7.373.el8_10

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-50190Nov 8, 2024 · ice: fix memleak in ice_init_tx_topology()
    22Monitor
  • ← EarlierCVE-2024-50191Nov 8, 2024 · ext4: don't set SB_RDONLY after filesystem errors
    22Monitor
  • Later →CVE-2024-50193Nov 8, 2024 · x86/entry_32: Clear CPU buffers after register restore in NMI return
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux01282ab5182f85e42234df2ff42f0ce790f465ffVendor (CNA)
Linux Linux1442ee0011983f0c5c4b92380e6853afb513841aVendor (CNA)
Linux Linux64b12b061c5488e2d69e67c4eaae5da64fd30bfeVendor (CNA)
Linux Linux755b9532c885b8761fb135fedcd705e21e61cccbVendor (CNA)
Linux Linuxb7d7b7fc876f836f40bf48a87e07ea18756ba196Vendor (CNA)
Linux Linuxd960505a869e66184fff97fb334980a5b797c7c6Vendor (CNA)
azl3 kernel 6.6.57.1-7 on Azure Linux 3.06.6.64.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.64.2-1 on Azure Linux 3.06.6.64.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.167.1-2 on CBL-Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.173.1-1 on CBL Mariner 2.05.15.173.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.32.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.32.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.32.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.32.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.32.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.32.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.32.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.32.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.32.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.32.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.32.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.32.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.115-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-553.32.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.32.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.32.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.32.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.32.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.32.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+8

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records