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-37818LoongArch: Return NULL from huge_pte_offset() for invalid PMD

Description

In the Linux kernel, the following vulnerability has been resolved: LoongArch: Return NULL from huge_pte_offset() for invalid PMD LoongArch's huge_pte_offset() currently returns a pointer to a PMD slot even if the underlying entry points to invalid_pte_table (indicating no mapping). Callers like smaps_hugetlb_range() fetch this invalid entry value (the address of invalid_pte_table) via this pointer. The generic is_swap_pte() check then incorrectly identifies this address as a swap entry on LoongArch, because it satisfies the "!pte_present() && !pte_none()" conditions. This misinterpretation, combined with a coincidental match by is_migration_entry() on the address bits, leads to kernel crashes in pfn_swap_entry_to_page(). Fix this at the architecture level by modifying huge_pte_offset() to check the PMD entry's content using pmd_none() before returning. If the entry is invalid (i.e., it points to invalid_pte_table), return NULL instead of the pointer to the slot.

Timeline

  1. ID reserved

    By Linux

  2. · 22 days later

    Published

  3. · 12 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-37818, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (13 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected fa96b57c149061f71a70bd6582d995f6424fbbf4 – < 34256805720993e37adf6127371a1265aea8376a
    • affected fa96b57c149061f71a70bd6582d995f6424fbbf4 – < 2ca9380b12711afe95b3589bd82b59623b3c96b3
    • affected fa96b57c149061f71a70bd6582d995f6424fbbf4 – < 51424fd171cee6a33f01f7c66b8eb23ac42289d4
    • affected fa96b57c149061f71a70bd6582d995f6424fbbf4 – < b49f085cd671addbda4802d6b9382513f7dd0f30
    • affected fa96b57c149061f71a70bd6582d995f6424fbbf4 – < bd51834d1cf65a2c801295d230c220aeebf87a73
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 6.1.136 – ≤ 6.1.*
    • unaffected 6.6.89 – ≤ 6.6.*
    • unaffected 6.12.26 – ≤ 6.12.*
    • unaffected 6.14.5 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .