CVE-2025-38195: Linux kernel · LoongArch: Fix panic caused by NULL-PMD in huge_pte_offset()
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in ee084fa96123ede8b0563a1b5a9b23adc43cd50d : update Linux kernel when convenient.
Data as of 30 Oct 2026, 16:33 UTC
Thin evidence
One scorer or none- Patch
- Available – fixed in ee084fa96123ede8b0563a1b5a9b23adc43cd50d, b427d98d55217b53c88643579fbbd8a4c351a105, b5c7397b7fd125203c60b59860c168ee92291272 +6
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: LoongArch: Fix panic caused by NULL-PMD in huge_pte_offset() ERROR INFO: CPU 25 Unable to handle kernel paging request at virtual address 0x0 ... Call Trace: [<900000000023c30c>] huge_pte_offset+0x3c/0x58 [<900000000057fd4c>] hugetlb_follow_page_mask+0x74/0x438 [<900000000051fee8>] __get_user_pages+0xe0/0x4c8 [<9000000000522414>] faultin_page_range+0x84/0x380 [<9000000000564e8c>] madvise_vma_behavior+0x534/0xa48 [<900000000056689c>] do_madvise+0x1bc/0x3e8 [<9000000000566df4>] sys_madvise+0x24/0x38 [<90000000015b9e88>] do_syscall+0x78/0x98 [<9000000000221f18>] handle_syscall+0xb8/0x158 In some cases, pmd may be NULL and rely on NULL as the return value for processing, so it is necessary to determine this situation here.
References
- nvd.nist.gov/vuln/detail/CVE-2025-38195 (opens in a new tab)
- git.kernel.org/stable/c/55a9a7d21309bbea1dd629cf28396521a2803bb3 (opens in a new tab)
- git.kernel.org/stable/c/985f086f281b7bbb6644851e63af1a17ffff9277 (opens in a new tab)
- git.kernel.org/stable/c/b427d98d55217b53c88643579fbbd8a4c351a105 (opens in a new tab)
- git.kernel.org/stable/c/b5c7397b7fd125203c60b59860c168ee92291272 (opens in a new tab)
- git.kernel.org/stable/c/ee084fa96123ede8b0563a1b5a9b23adc43cd50d (opens in a new tab)