CVE-2025-39992mm: swap: check for stable address space before operating on the VMA
- —Not scoredno CVSS score yet
- 0.20%Exploitation in 30 daysEPSS · top 90% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: mm: swap: check for stable address space before operating on the VMA It is possible to hit a zero entry while traversing the vmas in unuse_mm() called from swapoff path and accessing it causes the OOPS: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000446--> Loading the memory from offset 0x40 on the XA_ZERO_ENTRY as address. Mem abort info: ESR = 0x0000000096000005 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x05: level 1 translation fault The issue is manifested from the below race between the fork() on a process and swapoff: fork(dup_mmap()) swapoff(unuse_mm) --------------- ----------------- 1) Identical mtree is built using __mt_dup(). 2) copy_pte_range()--> copy_nonpresent_pte(): The dst mm is added into the mmlist to be visible to the swapoff operation. 3) Fatal signal is sent to the parent process(which is the current during the fork) thus skip the duplication of the vmas and mark the vma range with XA_ZERO_ENTRY as a marker for this process that helps during exit_mmap(). 4) swapoff is tried on the 'mm' added to the 'mmlist' as part of the 2. 5) unuse_mm(), that iterates through the vma's of this 'mm' will hit the non-NULL zero entry and operating on this zero entry as a vma is resulting into the oops. The proper fix would be around not exposing this partially-valid tree to others when droping the mmap lock, which is being solved with [1]. A simpler solution would be checking for MMF_UNSTABLE, as it is set if mm_struct is not fully initialized in dup_mmap(). Thanks to Liam/Lorenzo/David for all the suggestions in fixing this issue.
Timeline
ID reserved
By Linux
- 6 months later
· 6 months later
Published
- 7 months later
· 7 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
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.
- EPSS (exploitation in 30 days)
- 0.20% · top 90% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected d2406291483775ecddaee929231a39c70c08fda2 – < 4e5f060d7347466f77aaff1c0d5a6c4f1fb217ac
- affected d2406291483775ecddaee929231a39c70c08fda2 – < 9cddad3b26dac830407d2d3c0de5205ff6d6dda0
- affected d2406291483775ecddaee929231a39c70c08fda2 – < e4e99d69b8b8295c501b2eef89e13306b738b667
- affected d2406291483775ecddaee929231a39c70c08fda2 – < 1367da7eb875d01102d2ed18654b24d261ff5393
- affected 6.8
- unaffected < 6.8
- unaffected 6.12.51 – ≤ 6.12.*
- unaffected 6.16.11 – ≤ 6.16.*
- unaffected 6.17.1 – ≤ 6.17.*
- unaffected 6.18 – ≤ *
References
References4
- https://git.kernel.org/stable/c/4e5f060d7347466f77aaff1c0d5a6c4f1fb217ac (opens in a new tab)
- https://git.kernel.org/stable/c/9cddad3b26dac830407d2d3c0de5205ff6d6dda0 (opens in a new tab)
- https://git.kernel.org/stable/c/e4e99d69b8b8295c501b2eef89e13306b738b667 (opens in a new tab)
- https://git.kernel.org/stable/c/1367da7eb875d01102d2ed18654b24d261ff5393 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-34581 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-39992)Record last updated .