{"uuid": "2ebe0f7a-be4a-4698-982a-1f4e74932c02", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37819", "type": "published-proof-of-concept", "source": "https://t.me/cvedetector/24806", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37819 - \"Linux Kernel GICv2m Use After Free Vulnerability in irqchip\"\", \n  \"Content\": \"CVE ID : CVE-2025-37819 \nPublished : May 8, 2025, 7:15 a.m. | 2\u00a0hours, 2\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nirqchip/gic-v2m: Prevent use after free of gicv2m_get_fwnode()  \n  \nWith ACPI in place, gicv2m_get_fwnode() is registered with the pci  \nsubsystem as pci_msi_get_fwnode_cb(), which may get invoked at runtime  \nduring a PCI host bridge probe. But, the call back is wrongly marked as  \n__init, causing it to be freed, while being registered with the PCI  \nsubsystem and could trigger:  \n  \n Unable to handle kernel paging request at virtual address ffff8000816c0400  \n  gicv2m_get_fwnode+0x0/0x58 (P)  \n  pci_set_bus_msi_domain+0x74/0x88  \n  pci_register_host_bridge+0x194/0x548  \n  \nThis is easily reproducible on a Juno board with ACPI boot.  \n  \nRetain the function for later use. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 May 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-05-08T11:45:06.000000Z"}