System crash via freed GICv2m callback
Published May 8, 2025 · Updated Jun 11, 2026
Use-after-free in the Linux kernel allows local users to crash an ACPI-based system during a runtime PCI host bridge probe. The gicv2m_get_fwnode callback in drivers/irqchip/irq-gic-v2m.c remains registered after its __init-marked code is freed, so PCI later dereferences released memory. Reachability requires an ACPI boot and a compatible GICv2m platform; the upstream report reproduces the paging fault on an Arm Juno board.
Summary
What happened
Use-after-free in the Linux kernel allows local users to crash an ACPI-based system during a runtime PCI host bridge probe. The gicv2m_get_fwnode callback in drivers/irqchip/irq-gic-v2m.c remains registered after its __init-marked code is freed, so PCI later dereferences released memory. Reachability requires an ACPI boot and a compatible GICv2m platform; the upstream report reproduces the paging fault on an Arm Juno board.
The record
- CVE
- CVE-2025-37819
- Published
- May 8, 2025
- Updated
- Jun 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 8, 2025CVE publishedPublication date reported by the CVE source.
- Jun 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0644b3daca28dcb320373ae20069c269c9386304 <0c241dedc43a036599757cd08f356253fa3e5014
- Affected versionversion=0644b3daca28dcb320373ae20069c269c9386304 <2f2803e4b5e4df2b08d378deaab78b1681ef9b30
- Affected versionversion=0644b3daca28dcb320373ae20069c269c9386304 <3318dc299b072a0511d6dfd8367f3304fb6d9827
- Affected versionversion=0644b3daca28dcb320373ae20069c269c9386304 <3939d6f29d34cdb60e3f68b76e39e00a964a1d51
- Affected versionversion=0644b3daca28dcb320373ae20069c269c9386304 <47bee0081b483b077c7560bc5358ad101f89c8ef
- Affected versionversion=0644b3daca28dcb320373ae20069c269c9386304 <b63de43af8d215b0499eac28b2caa4439183efc1
- Affected versionversion=0644b3daca28dcb320373ae20069c269c9386304 <dc0d654eb4179b06d3206e4396d072108b9ba082
- Affected versionversion=0644b3daca28dcb320373ae20069c269c9386304 <f95659affee301464f0d058d528d96b35b452da8
- Affected versionversion=4.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo