Vulnerability-Lookup

GHSA-QXC6-78Q3-77VP

Vulnerability from github – Published: 2026-08-27 06:31 – Updated: 2026-08-27 06:31

Details

In the Linux kernel, the following vulnerability has been resolved:

xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN

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.

Severity

7.1 (High)


                  
                    CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-80530"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-26T15:17:06Z",
    "severity": "HIGH"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nxfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN\n\nWhen exchanging two full-file ranges, xmi_can_exchange_reflink_flags()\ncan move the reflink inode flag from the file that currently has it to\nthe other file, as long as exactly one side is marked.  This assumes\nthat the file contents, and therefore all shared extents, are exchanged.\n\nThat assumption is not true when XFS_EXCHMAPS_INO1_WRITTEN is set.\nxfs_exchmaps_can_skip_mapping() can skip hole and unwritten mappings\nfrom file1, so an exchange can complete without moving every mapping\nthat the earlier flag-swap decision accounted for.  In that case the\npost-operation cleanup can clear the reflink flag from an inode that\nstill owns shared written extents.  Later writes then take the\nnon-reflink write path and may update blocks that should still have\nbeen protected by CoW, which shows up as data corruption between\nreflink-related files.\n\nFix this by disabling the reflink flag exchange whenever\nXFS_EXCHMAPS_INO1_WRITTEN is requested.  The contents exchange can still\nproceed; the conservative outcome is that both inodes keep the reflink\nflag.  The regular reflink flag cleanup path can drop the extra flag\nlater once the inode no longer has shared extents.",
  "id": "GHSA-qxc6-78q3-77vp",
  "modified": "2026-08-27T06:31:31Z",
  "published": "2026-08-27T06:31:31Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80530"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/03c9c9116e6da641424681f705698d7f5e2128e0"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/0f27b22343b63e10773e6781344640c2c753eec3"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/2efbd8890b53f4756fdc7b0ef346fa514ffb7d66"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b2d5a81dae385333f9734910277fbf94c78bd17f"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2026-80530 (GCVE-0-2026-80530)

Vulnerability from cvelistv5 – Published: 2026-08-26 14:37 – Updated: 2026-08-27 05:01

Title

xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN

Summary

In the Linux kernel, the following vulnerability has been resolved: xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN 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.

Severity

7.1 (High)


                        
                          CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Assigner

Linux mitre root

References

4 references

URL	Tags
https://git.kernel.org/stable/c/2efbd8890b53f4756…
https://git.kernel.org/stable/c/0f27b22343b63e107…
https://git.kernel.org/stable/c/03c9c9116e6da6414…
https://git.kernel.org/stable/c/b2d5a81dae385333f…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 966ceafc7a437105ecfe1cadb3747b2965a260ca , < 2efbd8890b53f4756fdc7b0ef346fa514ffb7d66 (git) Affected: 966ceafc7a437105ecfe1cadb3747b2965a260ca , < 0f27b22343b63e10773e6781344640c2c753eec3 (git) Affected: 966ceafc7a437105ecfe1cadb3747b2965a260ca , < 03c9c9116e6da641424681f705698d7f5e2128e0 (git) Affected: 966ceafc7a437105ecfe1cadb3747b2965a260ca , < b2d5a81dae385333f9734910277fbf94c78bd17f (git)
Linux	Linux	Affected: 6.10 Unaffected: 0 , < 6.10 (semver) Unaffected: 6.12.105 , ≤ 6.12.* (semver) Unaffected: 6.18.46 , ≤ 6.18.* (semver) Unaffected: 7.1.10 , ≤ 7.1.* (semver) Unaffected: 7.2 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/xfs/libxfs/xfs_exchmaps.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "2efbd8890b53f4756fdc7b0ef346fa514ffb7d66",
              "status": "affected",
              "version": "966ceafc7a437105ecfe1cadb3747b2965a260ca",
              "versionType": "git"
            },
            {
              "lessThan": "0f27b22343b63e10773e6781344640c2c753eec3",
              "status": "affected",
              "version": "966ceafc7a437105ecfe1cadb3747b2965a260ca",
              "versionType": "git"
            },
            {
              "lessThan": "03c9c9116e6da641424681f705698d7f5e2128e0",
              "status": "affected",
              "version": "966ceafc7a437105ecfe1cadb3747b2965a260ca",
              "versionType": "git"
            },
            {
              "lessThan": "b2d5a81dae385333f9734910277fbf94c78bd17f",
              "status": "affected",
              "version": "966ceafc7a437105ecfe1cadb3747b2965a260ca",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/xfs/libxfs/xfs_exchmaps.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.10"
            },
            {
              "lessThan": "6.10",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.105",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.46",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.1.*",
              "status": "unaffected",
              "version": "7.1.10",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.105",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.18.46",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.1.10",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "6.10",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nxfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN\n\nWhen exchanging two full-file ranges, xmi_can_exchange_reflink_flags()\ncan move the reflink inode flag from the file that currently has it to\nthe other file, as long as exactly one side is marked.  This assumes\nthat the file contents, and therefore all shared extents, are exchanged.\n\nThat assumption is not true when XFS_EXCHMAPS_INO1_WRITTEN is set.\nxfs_exchmaps_can_skip_mapping() can skip hole and unwritten mappings\nfrom file1, so an exchange can complete without moving every mapping\nthat the earlier flag-swap decision accounted for.  In that case the\npost-operation cleanup can clear the reflink flag from an inode that\nstill owns shared written extents.  Later writes then take the\nnon-reflink write path and may update blocks that should still have\nbeen protected by CoW, which shows up as data corruption between\nreflink-related files.\n\nFix this by disabling the reflink flag exchange whenever\nXFS_EXCHMAPS_INO1_WRITTEN is requested.  The contents exchange can still\nproceed; the conservative outcome is that both inodes keep the reflink\nflag.  The regular reflink flag cleanup path can drop the extra flag\nlater once the inode no longer has shared extents."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.1,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The flaw is only reachable via xfs_ioc_exchange_range()/xfs_ioc_commit_range() through XFS_IOC_EXCHANGE_RANGE or XFS_IOC_COMMIT_RANGE ioctl on open XFS file descriptors; there is no nfsd, ksmbd, or network packet path to xfs_exchmaps_clear_reflink().\nAC:L - A local attacker can craft reflinked files with hole/unwritten mappings, open both files read-write, and call exchange-range with XFS_EXCHANGE_RANGE_FILE1_WRITTEN|TO_EOF to deterministically skip mappings and trigger incorrect post-op reflink-flag clearing.\nPR:L - XFS_IOC_EXCHANGE_RANGE has no CAP_SYS_ADMIN gate and only requires DAC write on both exchanged files plus read access to reflink-clone a victim file; unprivileged users on shared multi-tenant XFS mounts meet this without init-namespace root.\nUI:N - Exploitation requires only the attacker\u0027s own ioctl calls on files they control; no separate victim must mount media, click prompts, or perform actions beyond storing readable data the attacker reflinks.\nS:U - Impact is on-disk data corruption or commingling between reflink-linked files within the same host kernel/filesystem authority; it does not cross VM, container network, or IOMMU boundaries like a hypervisor escape.\nC:H - Clearing the reflink inode flag while shared written extents remain breaks CoW isolation, so subsequent non-reflink writes can commingle or overwrite blocks still linked to other users\u0027 reflink clones, leaking data CoW should have kept private.\nI:H - After the incorrect reflink-flag clear, writes take the non-reflink path and directly modify shared storage blocks, letting an attacker corrupt content in other users\u0027 reflink-linked files without write permission to those inodes.\nA:N - The failure is logical metadata mishandling causing cross-file data corruption; it does not trigger kernel oops, panic, BUG_ON, or hang, and the fix commit describes only data corruption between reflink-related files, not system unavailability."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-27T05:01:24.159Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/2efbd8890b53f4756fdc7b0ef346fa514ffb7d66"
        },
        {
          "url": "https://git.kernel.org/stable/c/0f27b22343b63e10773e6781344640c2c753eec3"
        },
        {
          "url": "https://git.kernel.org/stable/c/03c9c9116e6da641424681f705698d7f5e2128e0"
        },
        {
          "url": "https://git.kernel.org/stable/c/b2d5a81dae385333f9734910277fbf94c78bd17f"
        }
      ],
      "title": "xfs: fix exchange-range reflink flag clearing issue with INO1_WRITTEN",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-80530",
    "datePublished": "2026-08-26T14:37:07.990Z",
    "dateReserved": "2026-08-26T14:34:25.764Z",
    "dateUpdated": "2026-08-27T05:01:24.159Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Detection rules are retrieved from Rulezet.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.

Action not permitted

GHSA-QXC6-78Q3-77VP

CVE-2026-80530 (GCVE-0-2026-80530)

Tags

Sightings

Nomenclature