{"uuid": "d9a4f55f-c614-4b9d-b35d-0d72abca093a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-37818", "type": "seen", "source": "https://t.me/cvedetector/24804", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-37818 - LoongArch Linux Kernel Invalid PMD Pointer Dereference Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-37818 \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  \nLoongArch: Return NULL from huge_pte_offset() for invalid PMD  \n  \nLoongArch's huge_pte_offset() currently returns a pointer to a PMD slot  \neven if the underlying entry points to invalid_pte_table (indicating no  \nmapping). Callers like smaps_hugetlb_range() fetch this invalid entry  \nvalue (the address of invalid_pte_table) via this pointer.  \n  \nThe generic is_swap_pte() check then incorrectly identifies this address  \nas a swap entry on LoongArch, because it satisfies the \"!pte_present()  \n&& !pte_none()\" conditions. This misinterpretation, combined with a  \ncoincidental match by is_migration_entry() on the address bits, leads to  \nkernel crashes in pfn_swap_entry_to_page().  \n  \nFix this at the architecture level by modifying huge_pte_offset() to  \ncheck the PMD entry's content using pmd_none() before returning. If the  \nentry is invalid (i.e., it points to invalid_pte_table), return NULL  \ninstead of the pointer to the slot. \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:01.000000Z"}