[CVE-2026-72108][MODERATE REGULAR] dm thin metadata: fix metadata snapshot consistency on commit failure

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

CVE: CVE-2026-72108
Priority: MODERATE REGULAR
AL-KERNEL base severity: MODERATE
KPANIC flag: NO
Patch: dm thin metadata: fix metadata snapshot consistency on commit failure
Commit: 4af993468193cf4cd32ba5748786e7801945f7d2
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4af993468193cf4cd32ba5748786e7801945f7d2
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-72108
Analysis date: Sat, 15 Aug 2026 21:41:16 -0400
ActionableScore: 4
ActionableScore lower bound: 2
Actionable bucket: Borderline, manual review recommended
Manual review required: YES

Summary:
dm thin metadata snapshot handling can persist an inconsistent held_root after metadata commit failure, causing thin pool metadata corruption, possible data loss, and pool unavailability when a privileged or delegated storage controller can trigger snapshot reserve or release operations.

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

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

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: YES

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

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

CVE-2026-72108	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:L/I:H/A:H';CWE-703;CWE-754;*CWE-664;Other CVSS 'AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:H/A:H';BEST CVSS score: '6.5';DESCR 'dm thin metadata snapshot handling could persist an inconsistent held_root if reserve or release updated the superblock buffer and the following metadata commit failed. This can corrupt thin pool metadata on disk, leading to bad reference counts, leaked metadata blocks, stale snapshot references, and possible data loss or pool unavailability. For the CVSS the PR:L in the paranoid score reflects environments where a reduced capability root, service account, or container admin can control device mapper targets or thin pool messages. The issue is local and is not network reachable. Impact is mainly integrity and availability of storage metadata, with only limited confidentiality concern from possible inconsistent block ownership scenarios.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Borderline, manual review recommended (with actual score 3)	YES	LOCK DISK LEAK HARDWARE LINUS  INCREASED_FROM_LOW_BASED_ON_REQUIREMANUALCHECK DECREASED_TO_MODERATEREG_BASED_ON_ACTIONABLESCORELESSTHAN5	NO	NO	checked

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

ActionableScore=4
ActionableScoreLower=2

## 1. ActionableScore

* Conservative score: 2
* Paranoid score: 4
* Final recommended bucket: **Borderline, manual review recommended**

## 2. Signal breakdown

Conservative signals:

* Important filesystem/storage path: +1. The bug is in dm thin metadata transaction handling and can persist inconsistent thin pool metadata.
* Integrity impact plausible: +1. The demonstrated result is bad metadata reference counts, stale held_root state, and metadata inconsistency.
* Availability impact realistic: +1. Persistent metadata inconsistency can make a thin pool unusable or require offline repair.
* Requires admin/root/CAP_SYS_ADMIN in typical deployments: -2. Creating dm targets and sending thin pool metadata snapshot messages normally requires privileged device mapper control.
* Hard or special trigger condition: -1. The reproducer requires forcing metadata commit failure with a crafted failing metadata device region.

Paranoid additional interpretation:

* Reduced capability storage administrator or service account model: +1 relative to conservative handling. In managed storage environments, a non full host root service or delegated admin may control thin pool messages.
* Persistent storage metadata corruption makes this more actionable than a transient warning or crash. It can affect data integrity after the triggering operation completes.

Not awarded:

* No generic kernel memory corruption bonus. The patch shows on disk metadata inconsistency, not UAF, OOB write, double free, or type confusion in kernel heap memory.
* No remote/network trigger. The affected path is local device mapper control plane.
* No privilege escalation bonus. The patch does not support a concrete LPE primitive.

## 3. Reachability analysis

The realistic trigger is a local privileged actor able to configure device mapper thin pools and issue reserve_metadata_snap or release_metadata_snap messages. In normal deployments this maps to root or CAP_SYS_ADMIN, so the conservative score is low. Namespaces usually do not make host device mapper broadly available, but storage management services, containerized storage stacks, or reduced capability root contexts may lower the practical privilege boundary. The path is not network reachable by itself, but it may be reachable indirectly through a storage management API that controls dm thin pools.

Call-site confidence: high, because the patch includes the affected reserve, release, get, begin, open, and commit paths.

## 4. Severity interpretation

This behaves more like a borderline actionable Moderate than an Important kernel memory corruption issue. The impact is persistent storage metadata corruption with integrity and availability consequences, not a demonstrated kernel code execution or privilege escalation primitive. The conservative score remains low because the trigger normally requires administrative device mapper control and a commit failure condition. The paranoid score is higher because delegated storage control can be a meaningful operational security boundary and persistent metadata corruption should not be auto-closed without checking deployment exposure.

## 5. One-sentence report phrase

dm thin metadata snapshot handling can persist an inconsistent held_root after metadata commit failure, causing thin pool metadata corruption, possible data loss, and pool unavailability when a privileged or delegated storage controller can trigger snapshot reserve or release operations.

## 6. Manual review recommendation

MANUAL CHECK RECOMMENDED

Persistent storage metadata corruption can have operational integrity impact beyond a transient DoS, but the issue normally requires privileged local device mapper control and does not show a kernel memory corruption or LPE primitive.

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

Patch: dm thin metadata: fix metadata snapshot consistency on commit failure
Commit: 4af993468193cf4cd32ba5748786e7801945f7d2
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=4af993468193cf4cd32ba5748786e7801945f7d2

Commit description:

__reserve_metadata_snap() and __release_metadata_snap() modify the
superblock's held_root directly in the block_manager's buffer. If the
subsequent metadata commit fails, the held_root gets flushed to disk
through the abort_transaction path, resulting in inconsistent metadata.

Reproducer 1: __reserve_metadata_snap()

1. Create a 2 MiB metadata device and make the region after the 14th
   block inaccessible, to trigger metadata commit failure in the
   subsequent reserve_metadata_snap operation. The 14th block will be
   the shadow destination for the index block.

dmsetup create tmeta --table "0 112 linear /dev/sdc 0
112 3984 error"

2. Create a 16 MiB thin-pool

dmsetup create tdata --table "0 32768 zero"
dd if=/dev/zero of=/dev/mapper/tmeta bs=4k count=1
dmsetup create tpool --table "0 32768 thin-pool /dev/mapper/tmeta \
/dev/mapper/tdata 128 0 1 skip_block_zeroing"

3. Take a metadata snapshot to trigger metadata commit failure and
   transaction abort. However, the held_root is written to disk,
   breaking metadata consistency.

dmsetup message tpool 0 "reserve_metadata_snap"

thin_check v1.2.2 result:

Bad reference count for metadata block 6.  Expected 2, but space map contains 1.
Bad reference count for metadata block 7.  Expected 2, but space map contains 1.
Bad reference count for metadata block 13.  Expected 1, but space map contains 0.

Reproducer 2: __release_metadata_snap()

1. Create a 2 MiB metadata device and make the region after the 16th
   block inaccessible, to trigger metadata commit failure in the
   subsequent release_metadata_snap operation. The 16th block will be
   the shadow destination for the index block.

dmsetup create tmeta --table "0 128 linear /dev/sdc 0
128 3968 error"

2. Create a 16 MiB thin-pool

dmsetup create tdata --table "0 32768 zero"
dd if=/dev/zero of=/dev/mapper/tmeta bs=4k count=1
dmsetup create tpool --table "0 32768 thin-pool /dev/mapper/tmeta \
/dev/mapper/tdata 128 0 1 skip_block_zeroing"

3. Reserve then release the metadata snapshot, to trigger metadata
   commit failure and transaction abort. The held_root gets removed
   from the on-disk superblock, causing inconsistent metadata.

dmsetup message tpool 0 "reserve_metadata_snap"
dmsetup message tpool 0 "release_metadata_snap"

thin_check v1.2.2 result:

Bad reference count for metadata block 6.  Expected 1, but space map contains 2.
Bad reference count for metadata block 7.  Expected 1, but space map contains 2.
1 metadata blocks have leaked.

Fix by deferring the held_root update to commit time.

Additionally, move the existing-snapshot check in __reserve_metadata_snap
before the shadow operation to avoid unnecessary work. In
__release_metadata_snap, clear pmd->held_root before btree deletion so
partial failure leaks blocks rather than leaving a stale reference, and
unlock the snapshot block before decrementing its refcount.

Fixes: 991d9fa ("dm: add thin provisioning target")
Cc: stable@vger.kernel.org
Signed-off-by: Ming-Hung Tsai <mtsai@redhat.com>
Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  drivers/md/dm-thin-metadata.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=4af993468193cf4cd32ba5748786e7801945f7d2

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

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

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

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