[CVE-2026-64131][LOW] mm/memory: fix spurious warning when unmapping device-private/exclusive pages [ Upstream

[AL-KERNEL <alkernel@kernelcve.org>]

CVE: CVE-2026-64131
Priority: LOW
AL-KERNEL base severity: LOW
KPANIC flag: NO
Patch: mm/memory: fix spurious warning when unmapping device-private/exclusive pages [ Upstream
Commit: e81446b559db4c98a6c2c5e039ac9cb23658432e
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e81446b559db4c98a6c2c5e039ac9cb23658432e
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64131
Analysis date: Sun, 19 Jul 2026 14:33:11 -0400
ActionableScore: 2
ActionableScore lower bound: 1
Actionable bucket: Ordinary Moderate / Low-like
Manual review required: NO

Summary:
A local HMM or device-private memory user may trigger a spurious WARN_ON_ONCE during unmap of private file-backed mappings, but the issue appears limited to warning or panic_on_warn based DoS with no evidence of memory corruption or privilege escalation.

======================================================================
ABOUT THIS REPORT
======================================================================

The original Linux kernel CVE announcement for CVE-2026-64131 is available here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64131

The original announcement does not normally provide a security severity
estimate, CVSS assessment, or enough information to determine whether the
reported kernel bug represents a practically relevant security issue.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin. It combines
an autonomous classifier with LLM-assisted technical analysis and a
separate ActionableScore mechanism.

The purpose of this report is to prioritize Linux kernel CVEs before
manual review, identify cases that require prompt investigation, and
support automatic closure of issues that are unlikely to have meaningful
security impact.

Published priority for this report: LOW
Manual review required: NO

A detailed explanation of the methodology and priority rules is included
at the end of this message.

======================================================================
AL-KERNEL CLASSIFICATION RESULT
======================================================================

CVE-2026-64131	LOW	CHECK WITH IMPACT FROM ORIG NN LOW	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H';CWE-617;CWE-754;CWE-703;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L';BEST CVSS score: '4.7';DESCR 'A spurious WARN_ON_ONCE can occur in the mm unmap path for device-private or device-exclusive entries because the code checked whether the VMA was anonymous instead of checking whether the underlying folio was anonymous. A private file backed mapping can contain an anonymous folio after COW, so the old VMA based check can falsely warn during munmap or process teardown when HMM or device private migration is involved. For the CVSS the PR:L is used because triggering requires a local process with access to an HMM or device migration path, but it does not require full administrative control in all deployments. The issue is not network reachable. Impact is mainly a local availability issue through warning noise, and it may become a DoS only on systems where WARN is treated as fatal. No confidentiality or integrity impact is supported by the code path because the patch fixes an assertion condition rather than a stale pointer, UAF, OOB access, or arbitrary write primitive.';NO MANUAL CHECK; ,and ActionableScore result is Ordinary Moderate / Low-like (with actual score 2)	YES	READ INIT HARDWARE TEST MEMORY  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH DECREASED_TO_LOW_FROM_MODERATE_BASED_ON_ACTIONABLESCORELESSTHAN3	YES	NO	checked

======================================================================
ACTIONABLESCORE ANALYSIS
======================================================================

ActionableScore=2
ActionableScoreLower=1

## 1. ActionableScore

* Conservative score: 1
* Paranoid score: 2
* Final recommended bucket: **Ordinary Moderate / Low-like**

## 2. Signal breakdown

Conservative signals:

* Local trigger possible: +1. A local process can reach the unmap path, but the specific condition requires HMM/device-private or device-exclusive migration of an anonymous folio inside a private file-backed mapping.
* Rare and difficult-to-reach configuration: -1. The issue depends on HMM/device-private migration or similar device memory support, not a default generic mmap/munmap path for ordinary systems.
* WARN_ON continuation only: +1 at most, but conservative scoring treats this as weak because the patch and trace show a spurious warning, not UAF, OOB, double free, stale pointer reuse, or arbitrary write.

Paranoid signals:

* Local trigger possible: +1.
* Availability concern via WARN-as-fatal setups: +1. On systems with panic_on_warn or strict kernel warning policy, the warning may become a local DoS.
* No memory corruption bonus. The changed check only replaces vma_is_anonymous() with folio_test_anon() in a WARN_ON_ONCE condition.
* No confidentiality or integrity bonus. The patch does not show information disclosure, file-backed page corruption, UAF, OOB access, write primitive, or privilege boundary bypass.

Call-site confidence: high. The affected call path is visible in the trace and patch: munmap/process teardown -> unmap_vmas -> unmap_page_range -> zap_nonpresent_ptes.

## 3. Reachability analysis

The bug is locally reachable through process memory teardown or munmap after pages have been migrated to device-private memory. Practical triggering requires a system with HMM/device-private or device-exclusive support and a device or driver path that can migrate private file-backed mappings. It is not network reachable. Namespaces do not obviously turn this into a broad unprivileged primitive, although device node permissions may allow non-root GPU/HMM users to reach the condition in some deployments.

## 4. Severity interpretation

This behaves like a Low or ordinary Moderate issue, not an Important-class vulnerability. The realistic impact is a spurious kernel warning. The paranoid impact is local DoS only when warnings are configured as fatal. There is no supported memory corruption primitive and no practical privilege escalation evidence.

## 5. One-sentence report phrase

A local HMM or device-private memory user may trigger a spurious WARN_ON_ONCE during unmap of private file-backed mappings, but the issue appears limited to warning or panic_on_warn based DoS with no evidence of memory corruption or privilege escalation.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED.

Reason: the patch fixes an incorrect assertion condition, not object lifetime, bounds, ownership, page-cache corruption, or access-control logic. The issue can be handled as low-priority unless the affected product treats WARN as fatal or exposes HMM/device-private migration broadly to untrusted users.

======================================================================
UPSTREAM PATCH SUMMARY
======================================================================

Patch: mm/memory: fix spurious warning when unmapping device-private/exclusive pages [ Upstream
Commit: e81446b559db4c98a6c2c5e039ac9cb23658432e
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e81446b559db4c98a6c2c5e039ac9cb23658432e

Changed files:
  mm/memory.c
  tools/testing/selftests/vm/hmm-tests.c

Diff excerpt:

Not included in this email. See the upstream URL for the full patch.

Full patch:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=e81446b559db4c98a6c2c5e039ac9cb23658432e

======================================================================
DETAILED REPORT METHODOLOGY
======================================================================

The original Linux kernel CVE announcement for CVE-2026-64131 can be found here:
https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-64131

The original CVE announcement normally does not include a security-level
estimate. In particular, it may not contain a CVSS assessment, an impact
level, or enough information to determine whether the reported bug is a
practically relevant security issue. One purpose of this parallel CVE list
is to provide that missing technical and prioritization information.

The original goal of the AL-KERNEL project was to prioritize Linux kernel
CVE analysis automatically before manual review. The system can also help
identify non-security issues that may be suitable for automatic closure.

This report was generated by AL-KERNEL, an AI-assisted Linux kernel
vulnerability analysis system developed by Alexander Larkin.

The first analysis stage combines an autonomous classifier with additional
LLM-based analysis. The autonomous classifier runs locally on a CPU and is
based on a backpropagation neural network. Together, these mechanisms
produce a technical vulnerability description, identify likely weakness
types, estimate CVSS severity, and provide input for ActionableScore.

Two CVSS estimates are retained because incomplete kernel vulnerability
information often permits more than one defensible interpretation:

  Conservative CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS score: 4.7

The conservative vector represents a lower-impact interpretation.
The Best/paranoid vector intentionally represents a plausible upper-bound
interpretation and should not automatically be treated as demonstrated
real-world impact.

CVSS may also need to be adjusted for a particular Linux deployment,
because actual reachability, privileges, enabled kernel configuration,
hardware, namespaces, exposed device nodes, and other environmental
conditions can differ significantly between systems.

A separate ActionableScore mechanism evaluates practical remediation
urgency. Its analysis may include reachability, attack prerequisites,
subsystem exposure, memory-corruption characteristics, denial-of-service
reliability, and possible confidentiality, integrity, or
privilege-escalation impact.

  Conservative ActionableScore: 1
  Paranoid ActionableScore: 2

The final base severity is taken directly from the second tab-separated
field of the AL-KERNEL classification result. ActionableScore does not
replace or independently override that final AL-KERNEL decision, and
if ActionableScore adjusted impact level of ALKERNEL, then you would see
self-readable flags above like INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN7.

For an AL-KERNEL result of MODERATE, this report uses the following
additional presentation split:

  ActionableScore below 5   -> MODERATE REGULAR
  ActionableScore 5 or more -> MODERATE 7.0

The distinction between MODERATE REGULAR and MODERATE 7.0 makes it
possible to identify Moderate issues that should receive manual analysis
and fixes before lower-priority MODERATE REGULAR issues. In many cases,
MODERATE REGULAR fixes may wait for a later rebase or routine update.

There is one override in which MODERATE REGULAR becomes MODERATE 7.0
even when the ActionableScore is below 5. When the AL-KERNEL result
contains the KPANIC flag, a MODERATE result is always presented as
MODERATE 7.0. The KPANIC flag selected with few regexps without
usage of AI at all, so it helps to detect cases when Kernel Crash happens
and similar (to filter False-Negative results from the LLM usage).

KPANIC indicates that a reliable kernel crash, kernel panic, or similarly
serious kernel availability impact was identified by the classification
workflow.

AL-KERNEL base severity for this report: LOW
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): LOW

These results are intended to support engineering triage. They are
machine-generated estimates, and cases marked for manual review should
be validated by a human security engineer before final disposition.
For more info read docs linked from here: https://kernelcve.org/
(and you can submit you own patch there to generate such a report
for non-existant CVE-id yet).

Note that in many cases this AI tool selects higher severity, than
real is (means you can expect Importants instead of Moderate 7.0 or
Moderates 7.0 instead of regular Moderates). If you see such cases,
please use reply email interface to add additional manual analyses
info to this particular CVE.
And please, please, let me know when you see Lows instead of Importants
or Important instead of Low (because particular for such cases I
need to tune this AI tool to make it better for this one and next similar).
My contact email for such notifications is alexanjelausa@gmail.com (and both
send reply to CVE record itself too and see "reply" button below for howto reply).