Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 31/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.22% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 0c241dedc43a036599757cd08f356253fa3e5014, 2f2803e4b5e4df2b08d378deaab78b1681ef9b30, 3318dc299b072a0511d6dfd8367f3304fb6d9827; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.

Low priority for now. Upgrade to Linux Linux 0c241dedc43a036599757cd08f356253fa3e5014, 2f2803e4b5e4df2b08d378deaab78b1681ef9b30, 3318dc299b072a0511d6dfd8367f3304fb6d9827; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.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-v2m: Prevent use after free of gicv2m_get_fwnode() With ACPI in place, gicv2m_get_fwnode() is registered with the pci subsystem as pci_msi_get_fwnode_cb(), 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 gicv2m_get_fwnode+0x0/0x58 (P) pci_set_bus_msi_domain+0x74/0x88 pci_register_host_bridge+0x194/0x548 This is easily reproducible on a Juno board with ACPI boot. Retain the function for later use.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
May 8, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 13th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

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

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.

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
debiandebian linux

Affected versions

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

  • debian debian linux11.0
  • linux linux kernel5.5 and later · before 5.10.238
  • linux linux kernel5.11 and later · before 5.15.182
  • linux linux kernel5.16 and later · before 6.1.138
  • linux linux kernel4.5 and later · before 5.4.294
  • linux linux kernel6.7 and later · before 6.12.26
  • linux linux kernel6.13 and later · before 6.14.5
  • linux linux kernel6.2 and later · before 6.6.89
  • linux linux kernel6.15

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

    • 4.5affected
    • 0644b3daca28dcb320373ae20069c269c9386304 and later · before 0c241dedc43a036599757cd08f356253fa3e5014affected · git
    • 0644b3daca28dcb320373ae20069c269c9386304 and later · before b63de43af8d215b0499eac28b2caa4439183efc1affected · git
    • 0644b3daca28dcb320373ae20069c269c9386304 and later · before f95659affee301464f0d058d528d96b35b452da8affected · git
    • 0644b3daca28dcb320373ae20069c269c9386304 and later · before dc0d654eb4179b06d3206e4396d072108b9ba082affected · git
    • 0644b3daca28dcb320373ae20069c269c9386304 and later · before 2f2803e4b5e4df2b08d378deaab78b1681ef9b30affected · git
    • 0644b3daca28dcb320373ae20069c269c9386304 and later · before 3939d6f29d34cdb60e3f68b76e39e00a964a1d51affected · git
    • 0644b3daca28dcb320373ae20069c269c9386304 and later · before 47bee0081b483b077c7560bc5358ad101f89c8efaffected · git
    • 0644b3daca28dcb320373ae20069c269c9386304 and later · before 3318dc299b072a0511d6dfd8367f3304fb6d9827affected · git
    • before 4.5not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.31.1.el10_16.12.0-124.31.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.31.1.el10_16.12.0-124.31.1.el10_1
AlmaLinux:9kernelbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64kbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-corebefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-debugbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-develbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-corebefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-cross-headersbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-debugbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-debug-corebefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-debug-develbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-611.30.1.el9_75.14.0-611.30.1.el9_7

+96

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-2025-37817May 8, 2025 · mcb: fix a double free bug in chameleon_parse_gdd()
    31Monitor
  • ← EarlierCVE-2025-37818May 8, 2025 · LoongArch: Return NULL from huge_pte_offset() for invalid PMD
    22Monitor
  • Later →CVE-2025-37821May 8, 2025 · sched/eevdf: Fix se->slice being set to U64_MAX and resulting crash
    22Monitor

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 Linux0c241dedc43a036599757cd08f356253fa3e5014Vendor (CNA)
Linux Linux2f2803e4b5e4df2b08d378deaab78b1681ef9b30Vendor (CNA)
Linux Linux3318dc299b072a0511d6dfd8367f3304fb6d9827Vendor (CNA)
Linux Linux3939d6f29d34cdb60e3f68b76e39e00a964a1d51Vendor (CNA)
Linux Linux47bee0081b483b077c7560bc5358ad101f89c8efVendor (CNA)
Linux Linuxb63de43af8d215b0499eac28b2caa4439183efc1Vendor (CNA)
Linux Linuxdc0d654eb4179b06d3206e4396d072108b9ba082Vendor (CNA)
Linux Linuxf95659affee301464f0d058d528d96b35b452da8Vendor (CNA)
azl3 kernel 6.6.85.1-4 on Azure Linux 3.06.6.92.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.92.2-1 on Azure Linux 3.06.6.92.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-611.30.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-abi-stablelists6.12.0-124.31.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-doc6.12.0-124.31.1.el10_1 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.140-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.140-1~deb11u1 · Debian:11Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-570.81.1.el9_6 · Red Hat:rhel_eus:9.6::appstreamPackage registry (OSV)

+7

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.

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.
  • No special conditions are required; it is repeatable.

If successful

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

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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

All records