[CVE-2026-72213][MODERATE REGULAR] mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch [ Upstream

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

CVE: CVE-2026-72213
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch [ Upstream
Commit: 5c32ae4a91fb5f4941328e0c1720a7fa4189c3bd
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5c32ae4a91fb5f4941328e0c1720a7fa4189c3bd
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72213
Analysis date: Sat, 15 Aug 2026 21:00:55 -0400
ActionableScore: 4
ActionableScore lower bound: 3
Actionable bucket: Borderline Moderate. Not a Strong Important candidate and not Actionable Moderate at minimum
Manual review required: NO

Summary:
A hugetlb cgroup accounting mismatch can store the wrong cgroup pointer for reserved charges, causing incorrect uncharge behavior, page_counter underflow, and possible local DoS or limited resource accounting integrity impact.

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

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

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 REGULAR
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-72213	MODERATE	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:L/A:H';CWE-682;*CWE-664;**CWE-400;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L';BEST CVSS score: '5.3';DESCR 'A hugetlb cgroup accounting bug can store the wrong cgroup pointer in the folio reserved charge slot because the same h_cg variable is reused for reserved and non reserved charge paths. When the folio is later freed, the reserved uncharge path can decrement a counter that was never charged for that cgroup, causing page_counter underflow and a kernel warning. For the CVSS the PR:L is used because reliable triggering requires a local process that can create or use hugetlb mappings in a configured hugetlb cgroup environment. The issue is not network reachable. Impact is mainly local denial of service and resource accounting corruption. For the paranoid score, the highest still defensible interpretation is limited integrity impact from hugetlb cgroup policy accounting corruption and high availability impact if repeated triggering or panic_on_warn causes service disruption.';NO MANUAL CHECK; ,and ActionableScore result is Borderline Moderate. Not a Strong Important candidate and not Actionable Moderate at minimum (with actual score 4)	YES	OOB LINUS SYZBOT MEMORY  DECREASED_TO_MODERATE_REGULAR_FROM_MODERATE7_BASED_ON_GUESSCVSS_AND_CIANNH	NO	NO	checked

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

ActionableScore=4
ActionableScoreLower=3

## 1. ActionableScore

* Conservative score: 3
* Paranoid score: 4
* Final recommended bucket: **Borderline Moderate. Not a Strong Important candidate and not Actionable Moderate at minimum**

## 2. Signal breakdown

Triggered signals:

* Local unprivileged trigger: +1
  A local process may be able to create or use hugetlb mappings when hugetlb and cgroup configuration allows it. This is not remotely reachable.

* Cross-boundary isolation/policy bypass: +1
  The bug corrupts hugetlb cgroup accounting by uncharging the wrong cgroup. This can affect resource accounting between cgroups, but it is not a direct credential or namespace escape.

* Integrity impact plausible: +1
  Integrity is limited to resource accounting correctness. There is no evidence of arbitrary memory modification or file data corruption.

* Availability impact realistic: +1
  The demonstrated effect is page_counter underflow and WARN. In hardened deployments with panic_on_warn or repeated triggering, this can become a practical DoS.

Subtracted or not awarded:

* Rare AND difficult-to-reach subsystem/configuration: -1
  Triggering depends on hugetlb, hugetlb cgroup accounting, noreserve style behavior, and suitable mappings. This is not a default broad attack surface.

* No generic memory corruption awarded.
  The patch separates two cgroup pointer variables. It does not show UAF, double free, OOB access, arbitrary write, type confusion, or attacker controlled reclaim.

* No privilege escalation plausible awarded.
  The wrong pointer is used for accounting charge and uncharge paths, not for object lifetime control or code/data overwrite.

* No reliable kernel crash / strong DoS awarded in conservative score.
  The concrete symptom is WARN and counter underflow, not a demonstrated unconditional panic.

## 3. Reachability analysis

A local process can potentially trigger this if it can allocate hugetlb folios under a hugetlb cgroup setup where reserved and non reserved charges are both involved. Namespaces or containers may matter if hugetlb usage is delegated to workloads, because then a containerized or reduced privilege process could influence cgroup accounting. The issue is not network reachable. The affected path is not a common default interface for all local users, because hugetlb availability and cgroup limits are deployment dependent.

Call-site confidence: high. The patch and commit message describe the full charge, commit, free, and uncharge path.

## 4. Severity interpretation

This behaves like an ordinary to borderline Moderate resource accounting bug, not an Important kernel memory corruption issue. The theoretical concern is cgroup accounting corruption and possible DoS if WARNs are fatal or the mismatch is repeatedly triggered. Realistic exploitation evidence does not show UAF, object replacement, arbitrary write, information disclosure, or privilege escalation.

## 5. One-sentence report phrase

A hugetlb cgroup accounting mismatch can store the wrong cgroup pointer for reserved charges, causing incorrect uncharge behavior, page_counter underflow, and possible local DoS or limited resource accounting integrity impact.

## 6. Manual review recommendation

NO MANUAL CHECK NEEDED

This can be handled as non-urgent unless the product heavily relies on delegated hugetlb cgroup isolation or panic_on_warn is enabled.

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

Patch: mm/hugetlb: fix hugetlb cgroup rsvd charge/uncharge mismatch [ Upstream
Commit: 5c32ae4a91fb5f4941328e0c1720a7fa4189c3bd
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=5c32ae4a91fb5f4941328e0c1720a7fa4189c3bd

Changed files:
  mm/page_counter.c
  mm/hugetlb.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=5c32ae4a91fb5f4941328e0c1720a7fa4189c3bd

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

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

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

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: 3
  Paranoid ActionableScore: 4

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 REGULAR

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