In the Linux kernel, the following vulnerability has been resolved:
mm/rmap: fix potential out-of-bounds page table access during batched unmap
As pointed out by David[1], the batched unmap logic in
try_to_unmap_one() may read past the end of a PTE table when a large
folio's PTE mappings are not fully contained within a single page
table.
While this scenario might be rare, an issue triggerable from userspace
must be fixed regardless of its likelihood. This patch fixes the
out-of-bounds access by refactoring the logic into a new helper,
folio_unmap_pte_batch().
The new helper correctly calculates the safe batch size by capping the
scan at both the VMA and PMD boundaries. To simplify the code, it also
supports partial batching (i.e., any number of pages from 1 up to the
calculated safe maximum), as there is no strong reason to special-case
for fully mapped folios.
Security readout for executives and security teams
Plain-English summary
A local, low-privileged user may trigger an out-of-bounds page-table read in affected Linux kernels during a rare memory-unmapping condition. The supplied CVSS assessment rates potential confidentiality, integrity, and availability impact as high, but the sources do not demonstrate a specific compromise outcome.
Executive priority
Prioritize timely remediation on shared hosts, developer platforms, and systems where untrusted users can execute locally. Treat internet exposure alone as insufficient evidence of exploitability because the supplied vector is local. Accelerate action where kernel compromise would affect sensitive workloads or tenant isolation.
Technical view
Linux try_to_unmap_one() could scan beyond a PTE table when a large folio’s mappings cross a page-table boundary during batched unmapping. The kernel fix introduces folio_unmap_pte_batch() and caps batching at VMA and PMD boundaries. The supplied CVSS v3.1 score is 7.8, requiring local access and low privileges without user interaction.
Likely exposure
Systems running the affected Linux kernel versions identified in the CVE bundle, including the listed 6.15 range, warrant review. Exploitation requires local, low-privileged access. Distribution kernels may backport fixes, so version strings alone may not establish exposure.
Exploitation context
The issue is described as rare but triggerable from userspace. The supplied record is not in CISA KEV, and no cited source reports active exploitation or a public exploit. Evidence supports treating it as a local kernel security risk, not an established remote threat.
Researcher notes
The vulnerable path involves batched reverse-mapping unmap logic and large folios whose PTE mappings span a page-table boundary. The fix bounds scans at VMA and PMD limits and permits partial batches. The sources establish an out-of-bounds read but do not document reproducibility, exploit reliability, downstream backports, or a demonstrated privilege-escalation chain.
Mitigation direction
Apply a vendor-supported kernel containing the cited upstream or stable fix.
Reboot into the updated kernel after installation.
Prioritize multi-user systems and workloads granting untrusted users local execution.
Restrict unnecessary local access until affected systems are updated.
Check distribution advisories for backport status and supported remediation versions.
Validation and detection
Inventory running kernel versions across Linux systems.
Compare vendor package changelogs against CVE-2025-38447 and the cited fix commits.
Confirm the running kernel changed after patching and rebooting.
Verify distribution-specific scanners recognize the installed fix or backport.
Monitor kernel logs and crashes for memory-management anomalies while remediation proceeds.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-38447 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
3Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.