CVE-2025-37819: irqchip/gic-v2m: Prevent use after free of gicv2m_get_fwnode()

Published May 8, 2025
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

irqchip/gic-v2m: Prevent use after free of gicv2mgetfwnode()

With ACPI in place, gicv2mgetfwnode() is registered with the pci subsystem as pcimsigetfwnodecb(), which may get invoked at runtime during a PCI host bridge probe. But, the call back is wrongly marked as init, causing it to be freed, while being registered with the PCI subsystem and could trigger:

Unable to handle kernel paging request at virtual address ffff8000816c0400 gicv2mgetfwnode+0x0/0x58 (P) pcisetbusmsidomain+0x74/0x88 pciregisterhostbridge+0x194/0x548

This is easily reproducible on a Juno board with ACPI boot.

Retain the function for later use.

Affected Software

18 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=4.5<5.4.294
Linux Linux kernel>=5.5<5.10.238
Linux Linux kernel>=5.11<5.15.182
Linux Linux kernel>=5.16<6.1.138
Linux Linux kernel>=6.2<6.6.89
Linux Linux kernel>=6.7<6.12.26
Linux Linux kernel>=6.13<6.14.5
Linux Linux kernel=6.15-rc1
Linux Linux kernel=6.15-rc2
Linux Linux kernel=6.15-rc3
Debian Debian Linux=11.0
Microsoft azl3 kernel 6.6.92.2-1
Microsoft azl3 kernel 6.6.85.1-4
IBM Verify Identity Access<=11.0 - 11.0.2
IBM Security Verify Access<=10.0 - 10.0.9.1
IBM Verify Identity Access Container<=11.0 - 11.0.2
IBM Security Verify Access Container<=10.0 - 10.0.9.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Apply the resolved fix in the Linux kernel: ensure irqchip/gic-v2m retains the gicv2m_get_fwnode() function so it is not freed after __init while still registered with PCI (prevent use-after-free during pci_register_host_bridge / pci_set_bus_msi_domain and runtime callback pci_msi_get_fwnode_cb()).

    Linux kernel (irqchip/gic-v2m) gicv2m_get_fwnode lifecycle = Retain the function for later use (prevent use-after-free)

Event History

May 8, 2025
CVE Published
via MITRE·06:26 AM
Data Sourced
via MITRE·06:26 AM
Description
Data Sourced
via Red Hat·07:02 AM
DescriptionSeverityAffected Software
Data Sourced
via NVD·07:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 11, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Jul 8, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

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-2025-37819?

CVE-2025-37819 is categorized as a moderate severity vulnerability due to its potential for use after free issues in the Linux kernel.

2

How do I fix CVE-2025-37819?

To address CVE-2025-37819, update the Linux kernel to the latest stable version that contains the patch for this vulnerability.

3

Which systems are affected by CVE-2025-37819?

CVE-2025-37819 affects the Linux kernel, specifically systems utilizing the irqchip and ACPI configuration.

4

What are the potential consequences of CVE-2025-37819?

Exploitation of CVE-2025-37819 could lead to stability issues or arbitrary code execution by allowing access to freed memory.

5

Is CVE-2025-37819 part of a larger vulnerability series?

CVE-2025-37819 addresses a specific issue related to IRQ chip management in the Linux kernel, but it is not part of a known series.

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