[CVE-2026-72172][MODERATE 7.0] mm/mm_init: fix uninitialized struct pages for ZONE_DEVICE

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

CVE: CVE-2026-72172
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: mm/mm_init: fix uninitialized struct pages for ZONE_DEVICE
Commit: 511a60e71aec308b24722cffc1912bf6befb87bf
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=511a60e71aec308b24722cffc1912bf6befb87bf
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72172
Analysis date: Sat, 15 Aug 2026 22:19:47 -0400
ActionableScore: 5
ActionableScore lower bound: 2
Actionable bucket: Actionable Moderate at minimum
Manual review required: YES

Summary:
DAX memory hotplug into a specific early-section layout can leave ZONE_DEVICE tail struct pages uninitialized, creating a privileged local crash risk and a limited worst-case MM metadata corruption concern.

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

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

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: MODERATE 7.0
Manual review required: YES

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

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

CVE-2026-72172	MODERATE	CHECK WITH IMPACT FROM ORIG NN MODERATE	Maybe valid. Check manually. Hints by AL-KERNEL: The best (paranoid) CVSS is 'AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H';*CWE-457;CWE-665;CWE-908;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H';BEST CVSS score: '5.8';DESCR 'DAX memory hotplug into an unoccupied subsection of an early section can reuse an unoptimized boot memmap while compound page accounting assumes vmemmap optimization. This can leave remaining tail struct pages for ZONE_DEVICE uninitialized and later cause unexpected behavior or kernel crashes when those page metadata entries are used. For the CVSS the PR:L is used for the paranoid score because some deployments may delegate DAX or memory management operations to a local service account or reduced capability administrator, although typical systems require full administrative control. The issue is not network reachable and requires local control over DAX memory hotplug or a closely related management path. Impact is at least local denial of service via kernel crash and in worst case may allow limited confidentiality or integrity impact due to corrupted or uninitialized memory metadata, so it should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Actionable Moderate at minimum (with actual score 4)	YES	READ DANGER SIMPLEFIX MEMORY  DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	YES	NO	checked

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

ActionableScore=5
ActionableScoreLower=2

## 1. ActionableScore

* Conservative score: 2
* Paranoid score: 5
* Final recommended bucket: **Actionable Moderate at minimum**::

## 2. Signal breakdown

Conservative signals:

* Weak/indirect corruption candidate: +1
  Uninitialized `struct page` metadata can later be interpreted by core MM paths, but the patch does not show attacker-controlled overwrite, reclaim, type confusion, or arbitrary write.
* Reliable kernel crash / strong DoS: +1
  The commit explicitly says the uninitialized tail `struct page` entries can later lead to unexpected behavior or crashes.
* Privileged kernel/device-management memory corruption path: +1
  The issue is in ZONE_DEVICE / DAX memory hotplug and affects trusted kernel memory metadata.
* Requires admin/root/CAP_* in typical deployments: -2
  Reliable triggering normally requires DAX memory hotplug or device/memory management privileges.
* Rare AND difficult-to-reach subsystem/configuration: -1
  The affected condition requires DAX hotplug into an unoccupied subsection of an early section.

Paranoid additional signals:

* Local reduced-privilege trigger concern: +1
  Some deployments may delegate DAX or memory-management operations to a local service account or reduced-capability administrator.
* Confidentiality impact plausible: +1
  Uninitialized `struct page` metadata may in worst case affect page ownership or page-state interpretation, though no concrete leak primitive is shown.
* Integrity impact plausible: +1
  Corrupted or uninitialized page metadata may in worst case affect page lifecycle or mapping decisions, but no proven arbitrary write exists.
* Availability impact realistic: +1
  A later crash from invalid page metadata can be host-wide and not limited to a single failed operation.

## 3. Reachability analysis

The bug is not network reachable. It requires local control over DAX memory hotplug or a closely related memory/device-management path. In normal deployments this is an administrative operation, so the conservative interpretation treats it as requiring root or equivalent privileges. Namespaces and containers usually do not expose raw DAX hotplug control to unprivileged users, but specialized infrastructure may delegate memory or device-management actions to reduced-capability service accounts. The vulnerable path is not a broad default syscall path and depends on specific ZONE_DEVICE / DAX hotplug topology involving an early section.

Call-site confidence: medium. The patch provides the affected initialization path and the consequence for `memmap_init_compound()`, but not later crash call sites using the uninitialized tail `struct page` entries.

## 4. Severity interpretation

This is more than ordinary bookkeeping because it leaves core MM `struct page` metadata uninitialized. Realistic exploitation is most likely a privileged or semi-privileged local DoS through crashes after DAX hotplug. Theoretical confidentiality or integrity impact is plausible because `struct page` metadata is security-sensitive, but the patch does not demonstrate attacker-controlled reclaim, arbitrary write, type confusion, or a concrete LPE primitive. Therefore it is not a Strong Important candidate by default, but the paranoid score reaches Actionable Moderate and should not be auto-closed without review.

## 5. One-sentence report phrase

DAX memory hotplug into a specific early-section layout can leave ZONE_DEVICE tail struct pages uninitialized, creating a privileged local crash risk and a limited worst-case MM metadata corruption concern.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Core MM metadata initialization bugs can be underestimated, and this patch affects `struct page` state for ZONE_DEVICE memory. The realistic path is privileged and configuration-specific, but the possible impact goes beyond a simple warning or leak.

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

Patch: mm/mm_init: fix uninitialized struct pages for ZONE_DEVICE
Commit: 511a60e71aec308b24722cffc1912bf6befb87bf
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=511a60e71aec308b24722cffc1912bf6befb87bf

Commit description:

If DAX memory is hotplugged into an unoccupied subsection of an early
section, section_activate() reuses the unoptimized boot memmap.  However,
compound_nr_pages() still assumes that vmemmap optimization is in effect
and initializes only the reduced number of struct pages.  As a result, the
remaining tail struct pages are left uninitialized, which can later lead
to unexpected behavior or crashes.

Fix this by treating early sections as unoptimized when calculating how
many struct pages to initialize.

Link: https://lore.kernel.org/20260428081855.1249045-7-songmuchun@bytedance.com
Fixes: 6fd3620 ("mm/page_alloc: reuse tail struct pages for compound devmaps")
Signed-off-by: Muchun Song <songmuchun@bytedance.com>
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Acked-by: Liam R. Howlett <liam@infradead.org>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Cc: Joao Martins <joao.m.martins@oracle.com>
Cc: Lorenzo Stoakes <ljs@kernel.org>
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>
Cc: Michal Hocko <mhocko@suse.com>
Cc: Nicholas Piggin <npiggin@gmail.com>
Cc: Oscar Salvador <osalvador@suse.de>
Cc: Suren Baghdasaryan <surenb@google.com>
Cc: Vlastimil Babka <vbabka@kernel.org>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  mm/mm_init.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=511a60e71aec308b24722cffc1912bf6befb87bf

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

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

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:H/UI:N/S:U/C:N/I:N/A:H
  The Best / paranoid CVSS vector: AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
  The Best / paranoid CVSS score: 5.8

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: 2
  Paranoid ActionableScore: 5

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: MODERATE
KPANIC detected for this report: NO
Published priority for this report (same as in Subject): MODERATE 7.0

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).