Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 22 days later

    Published

  3. · 13 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-37819, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 0644b3daca28dcb320373ae20069c269c9386304 – < 0c241dedc43a036599757cd08f356253fa3e5014
    • affected 0644b3daca28dcb320373ae20069c269c9386304 – < b63de43af8d215b0499eac28b2caa4439183efc1
    • affected 0644b3daca28dcb320373ae20069c269c9386304 – < f95659affee301464f0d058d528d96b35b452da8
    • affected 0644b3daca28dcb320373ae20069c269c9386304 – < dc0d654eb4179b06d3206e4396d072108b9ba082
    • affected 0644b3daca28dcb320373ae20069c269c9386304 – < 2f2803e4b5e4df2b08d378deaab78b1681ef9b30
    • affected 0644b3daca28dcb320373ae20069c269c9386304 – < 3939d6f29d34cdb60e3f68b76e39e00a964a1d51
    • affected 0644b3daca28dcb320373ae20069c269c9386304 – < 47bee0081b483b077c7560bc5358ad101f89c8ef
    • affected 0644b3daca28dcb320373ae20069c269c9386304 – < 3318dc299b072a0511d6dfd8367f3304fb6d9827
  • Linux · Linux

    • affected 4.5
    • unaffected < 4.5
    • unaffected 5.4.294 – ≤ 5.4.*
    • unaffected 5.10.238 – ≤ 5.10.*
    • unaffected 5.15.182 – ≤ 5.15.*
    • unaffected 6.1.138 – ≤ 6.1.*
    • unaffected 6.6.89 – ≤ 6.6.*
    • unaffected 6.12.26 – ≤ 6.12.*
    • unaffected 6.14.5 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References10

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-37819 badge
[![CVE-2025-37819](https://cveledger.app/badge/CVE-2025-37819.svg)](https://cveledger.app/cve/CVE-2025-37819)

Record last updated .