Look up another CVE · open CVE-2025-38195 in the interactive tracker
CVE-2025-38195
LoongArch: Fix panic caused by NULL-PMD in huge_pte_offset()
Published 2025-07-04 (15 months ago) by the Linux kernel CNA. Subsystem arch/loongarch. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2025-38195 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | fixed | 6.12.35-1 | Update the kernel and reboot. Fixed in 6.12.35-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 6.12.35-1 | Update the kernel and reboot. Fixed in 6.12.35-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 6.12.35-1 | Update the kernel and reboot. Fixed in 6.12.35-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
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.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
arch/loongarch/mm/hugetlbpage.c
- What this is
- LOONGARCHMAINTAINERS section matched on arch/loongarch/ · loongarch@lists.linux.dev · Maintained
Check it on the machine
grep -w CONFIG_HUGETLB_PAGE /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookwormYnot built on armhf/armmp, armhf/rt/armmp
- trixieYnot built on armel/rpi, armhf/armmp, armhf/rt/armmp
- forky, sidYnot built on armhf/armmp
- Y
- built in where it is built at all; some flavours do not build it
- Build switch
- CONFIG_HUGETLB_PAGE
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2025-07-04 (15 months ago)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.18%, higher than 6.8% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- arch/loongarch
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.6.89 | 6.6.95 | b427d98d5521 |
| 6.12.26 | 6.12.35 | 985f086f281b |
| 6.15 | 6.15.4 | b5c7397b7fd1 |
| 6.15 | 6.16 | ee084fa96123 |
| 6.1.136 | 0 | 0 |
| 6.14.5 | 0 | 0 |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2025-38195, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.