[CVE-2026-80530][MODERATE 7.0] xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN

[CVE-2026-80530][MODERATE 7.0] xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN

[AL-KERNEL]

CVE: CVE-2026-80530
Priority: MODERATE 7.0
AL-KERNEL base severity: MODERATE
KPANIC flag: YES
Patch: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN
Commit: 2efbd8890b53f4756fdc7b0ef346fa514ffb7d66
Upstream patch: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2efbd8890b53f4756fdc7b0ef346fa514ffb7d66
Original CVE announcement: https://lore.kernel.org/linux-cve-announce/?q=CVE-2026-80530
Analysis date: Wed, 26 Aug 2026 13:53:58 -0400
ActionableScore: 7
ActionableScore lower bound: 6
Actionable bucket: Strong Important candidate / Actionable Moderate at minimum
Manual review required: YES

Summary:
An XFS exchange-range reflink flag handling bug can leave shared written extents on an inode that later uses the non-reflink write path, bypassing expected CoW protection and causing cross-file data corruption.

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

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

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-80530	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:H/A:H';CWE-693;*CWE-664;CWE-668;Other CVSS 'AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L';BEST CVSS score: '6.5';DESCR 'XFS exchange range can incorrectly clear the reflink inode flag when XFS_EXCHMAPS_INO1_WRITTEN is used and some hole or unwritten mappings from file1 are skipped. The inode may still own shared written extents, but later writes can take the non-reflink path and update blocks that should have been protected by CoW. This can corrupt data between reflink-related files and represents a file integrity failure rather than a kernel memory corruption primitive. For the CVSS the PR:L is used because a local process with access to the affected files and the exchange range operation may be enough to trigger the condition. The issue is not network reachable and has no direct evidence of kernel privilege escalation, but the cross-file data corruption impact should be reviewed manually.';YES REQUIRES MANUAL CHECK; ,and ActionableScore result is Strong Important candidate / Actionable Moderate at minimum (with actual score 7) 	MAYBE	DANGER DISK LINUS KPANIC  KPANIC INCREASED_TO_HIGH_BASED_ON_ACTIONABLESCOREHIGHEREQTHAN6 DECREASED_TO_MODERATE7_BASED_ON_FALSEPOSCHECKOFDH	-	-	checked

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

ActionableScore=7
ActionableScoreLower=6

## 1. ActionableScore

* Conservative score: 6
* Paranoid score: 7
* Final recommended bucket: **Strong Important candidate / Actionable Moderate at minimum**::

## 2. Signal breakdown

Triggered signals:

* Local unprivileged trigger: +1
  A local process with access to affected XFS files and the exchange-range operation may be able to trigger the condition. No network exposure is involved.

* Dirty-Pipe-like ownership/COW violation: +2
  The bug can clear the reflink flag from an inode that still owns shared written extents. Later writes may bypass the expected CoW path and modify physical blocks still shared with another reflink-related file.

* Filesystem/storage metadata corruption reachable by local user: +1
  The incorrect reflink flag state is filesystem metadata/state corruption that affects write-path correctness.

* Important filesystem/storage path: +1
  XFS reflink/CoW extent handling is an important filesystem integrity path.

* Integrity impact plausible: +1
  The commit explicitly states data corruption between reflink-related files.

* Availability impact realistic: +1
  Persistent filesystem data corruption can create practical availability impact beyond a transient crash.

* Practical exploit chain strongly implied: +1 paranoid only
  The chain write to one reflink-related inode -> missing CoW protection -> corruption of another shared extent is strongly implied by the patch context.

Subtracting signals:

* Special preconditions / complex setup: -1
  The issue requires XFS reflink, exchange-range, XFS_EXCHMAPS_INO1_WRITTEN, and a layout where skipped hole or unwritten mappings leave shared written extents behind.

No signals awarded for:

* Generic kernel memory corruption
  This is not a kernel UAF, OOB write, type confusion, or arbitrary write into kernel memory.

* Privilege escalation
  No concrete LPE primitive is shown.

* Remote reachability
  The affected path is local filesystem control/data path, not network-triggerable.

## 3. Reachability analysis

The bug is locally reachable when a user can operate on suitable XFS reflink-related files and invoke the exchange-range path with XFS_EXCHMAPS_INO1_WRITTEN. It does not require packet input or remote protocol parsing.

Typical triggering should not require full host root if ordinary file access and the relevant filesystem operation are available, so PR:L is the practical CVSS-style interpretation. Containers may matter if a container has writable access to an XFS-backed mount and the relevant ioctl/path is not blocked, but cross-container or host impact depends on mount sharing and file ownership.

The affected functionality is not a rare debug path, but it does require XFS reflink and a specific exchange-range optimization. Realistic exploitation is more constrained than a generic local syscall bug, but the demonstrated consequence is persistent cross-file data corruption.

Call-site confidence: medium. The patch and commit clearly describe the semantic failure in the exchange-range reflink flag decision, but the full ioctl permission path and all callers are not included in the supplied input.

## 4. Severity interpretation

This behaves as an actionable filesystem integrity vulnerability, not as ordinary low-risk filesystem corruption. The key issue is that CoW isolation can be bypassed after the reflink flag is incorrectly cleared, allowing later writes to affect blocks that should still be protected as shared extents.

Realistic evidence supports local data integrity corruption. Theoretical privilege escalation is not demonstrated and should not be assumed. However, because reflink/CoW bugs can cross file ownership or policy boundaries depending on file layout and permissions, this should not be auto-closed as an ordinary Moderate without manual review.

## 5. One-sentence report phrase

An XFS exchange-range reflink flag handling bug can leave shared written extents on an inode that later uses the non-reflink write path, bypassing expected CoW protection and causing cross-file data corruption.

## 6. Manual review recommendation

MANUAL CHECK REQUIRED

Reason: this is not kernel memory corruption, but it is a filesystem CoW/reflink ownership violation with plausible cross-file integrity impact and persistent data corruption, which is enough to require manual security review.

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

Patch: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN
Commit: 2efbd8890b53f4756fdc7b0ef346fa514ffb7d66
Upstream URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=2efbd8890b53f4756fdc7b0ef346fa514ffb7d66

Commit description:

When exchanging two full-file ranges, xmi_can_exchange_reflink_flags()
can move the reflink inode flag from the file that currently has it to
the other file, as long as exactly one side is marked.  This assumes
that the file contents, and therefore all shared extents, are exchanged.

That assumption is not true when XFS_EXCHMAPS_INO1_WRITTEN is set.
xfs_exchmaps_can_skip_mapping() can skip hole and unwritten mappings
from file1, so an exchange can complete without moving every mapping
that the earlier flag-swap decision accounted for.  In that case the
post-operation cleanup can clear the reflink flag from an inode that
still owns shared written extents.  Later writes then take the
non-reflink write path and may update blocks that should still have
been protected by CoW, which shows up as data corruption between
reflink-related files.

Fix this by disabling the reflink flag exchange whenever
XFS_EXCHMAPS_INO1_WRITTEN is requested.  The contents exchange can still
proceed; the conservative outcome is that both inodes keep the reflink
flag.  The regular reflink flag cleanup path can drop the extra flag
later once the inode no longer has shared extents.

Reported-by: Lin Jiapeng (TencentOS Red Team) <jiapenglin@tencent.com>
Fixes: 966ceaf ("xfs: create deferred log items for file mapping exchanges")
Cc: stable@vger.kernel.org # v6.10
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Lin Jiapeng <jiapenglin@tencent.com>
Signed-off-by: Carlos Maiolino <cem@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

Changed files:
  fs/xfs/libxfs/xfs_exchmaps.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=2efbd8890b53f4756fdc7b0ef346fa514ffb7d66

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

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

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:H/A:L
  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: 6
  Paranoid ActionableScore: 7

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