VulnerabilityPublished 27 Dec 2024Updated 30 Oct 2026

CVE-2024-53195: Linux kernel · KVM: arm64: Get rid of userspace_irqchip_in_use

Affects Linux kernelSource GCVE Database

Compare

Not known to be exploited.

Data as of 30 Oct 2026, 14:33 UTC

Severity

Medium

Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

A fix has been implemented in the Linux kernel by removing the userspace_irqchip_in_use static key and replacing its usage with a more reliable check. Users should update to the fixed Linux kernel version once available. No additional mitigation is required beyond applying the official kernel patch.

Description

CVE-2024-53195 is a vulnerability in the Linux kernel's KVM subsystem for arm64 architecture. It involves improper management of the userspace_irqchip_in_use static key, which can lead to a kernel warning (WARN_ON) during vCPU timer updates. The issue arises when userspace initializes a vCPU with PMU v3 but does not properly set up the virtual interrupt controller or PMU, causing an error path that leaves the irqchip usage state inconsistent. This flaw was addressed by removing the userspace_irqchip_in_use static key and replacing its functionality with a more reliable check.

Impact

This vulnerability can cause kernel warnings and potentially unstable behavior in the KVM arm64 virtualization subsystem when userspace mismanages vCPU initialization with PMU v3 and irqchip setup. It does not indicate direct code execution or privilege escalation but may affect stability and reliability of virtual machines using this configuration.

Summary

The vulnerability in the Linux kernel's KVM arm64 code is due to improper use of the userspace_irqchip_in_use static key. When userspace creates a VM and vCPU and initializes the vCPU with KVM_ARM_VCPU_PMU_V3 without setting up the virtual GIC or PMU, the kvm_arm_pmu_v3_enable() call fails. This failure causes KVM_RUN to return early without incrementing userspace_irqchip_in_use. If userspace retries initialization, the timer update code encounters an inconsistent state and triggers a WARN_ON() in kvm_timer_update_irq(). The fix removes the userspace_irqchip_in_use static key and replaces it with a check on irqchip_in_kernel(), preventing the mismanagement and the resulting kernel warning.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 30 Oct 2026, 14:33 UTC

Technical details

References

Community reviews

Related threats