Vulnerability-Lookup

GHSA-W48H-WV4W-HRQ6

Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32

Details

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

btrfs: zoned: fix deadlock waiting for ticket during data relocation

When performing data relocation on a zoned filesystem, BTRFS can deadlock in handle_reserve_tickets(). The relocation process is waiting on a space reservation ticket that can never be fulfilled, because the relocation itself is the operation responsible for freeing up that space.

Fix this by introducing a new flush state, BTRFS_RESERVE_FLUSH_ZONED_RELOCATION, specifically for data chunk allocation during zoned relocation. Like BTRFS_RESERVE_FLUSH_FREE_SPACE_INODE, this state uses priority_reclaim_data_space() instead of the normal flushing path, which avoids re-entering the relocation code and breaking the deadlock cycle.

In btrfs_alloc_data_chunk_ondemand(), select this new flush state when the inode belongs to a data relocation root on a zoned filesystem.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2026-74319"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-15T06:22:32Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: zoned: fix deadlock waiting for ticket during data relocation\n\nWhen performing data relocation on a zoned filesystem, BTRFS can deadlock\nin handle_reserve_tickets(). The relocation process is waiting on a space\nreservation ticket that can never be fulfilled, because the relocation\nitself is the operation responsible for freeing up that space.\n\nFix this by introducing a new flush state,\nBTRFS_RESERVE_FLUSH_ZONED_RELOCATION, specifically for data chunk\nallocation during zoned relocation. Like\nBTRFS_RESERVE_FLUSH_FREE_SPACE_INODE, this state uses\npriority_reclaim_data_space() instead of the normal flushing path, which\navoids re-entering the relocation code and breaking the deadlock cycle.\n\nIn btrfs_alloc_data_chunk_ondemand(), select this new flush state when the\ninode belongs to a data relocation root on a zoned filesystem.",
  "id": "GHSA-w48h-wv4w-hrq6",
  "modified": "2026-08-15T06:32:29Z",
  "published": "2026-08-15T06:32:29Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-74319"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/814c3b4ea357297c507158bceb07bcdc5fbe9808"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/f84dbbaa988e1344634a20ddf6c7d51a99f12477"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

CVE-2026-74319 (GCVE-0-2026-74319)

Vulnerability from cvelistv5 – Published: 2026-08-15 05:58 – Updated: 2026-08-17 05:17

Title

btrfs: zoned: fix deadlock waiting for ticket during data relocation

Summary

In the Linux kernel, the following vulnerability has been resolved: btrfs: zoned: fix deadlock waiting for ticket during data relocation When performing data relocation on a zoned filesystem, BTRFS can deadlock in handle_reserve_tickets(). The relocation process is waiting on a space reservation ticket that can never be fulfilled, because the relocation itself is the operation responsible for freeing up that space. Fix this by introducing a new flush state, BTRFS_RESERVE_FLUSH_ZONED_RELOCATION, specifically for data chunk allocation during zoned relocation. Like BTRFS_RESERVE_FLUSH_FREE_SPACE_INODE, this state uses priority_reclaim_data_space() instead of the normal flushing path, which avoids re-entering the relocation code and breaking the deadlock cycle. In btrfs_alloc_data_chunk_ondemand(), select this new flush state when the inode belongs to a data relocation root on a zoned filesystem.

Severity

No CVSS data available.

Assigner

Linux mitre root

References

2 references

URL	Tags
https://git.kernel.org/stable/c/f84dbbaa988e13446…
https://git.kernel.org/stable/c/814c3b4ea357297c5…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: e2a7fd22378f6500bcf979edc71e6837271eacfd , < f84dbbaa988e1344634a20ddf6c7d51a99f12477 (git) Affected: e2a7fd22378f6500bcf979edc71e6837271eacfd , < 814c3b4ea357297c507158bceb07bcdc5fbe9808 (git)
Linux	Linux	Affected: 7.1 Unaffected: 0 , < 7.1 (semver) Unaffected: 7.1.5 , ≤ 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/btrfs/delalloc-space.c",
            "fs/btrfs/space-info.c",
            "fs/btrfs/space-info.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "f84dbbaa988e1344634a20ddf6c7d51a99f12477",
              "status": "affected",
              "version": "e2a7fd22378f6500bcf979edc71e6837271eacfd",
              "versionType": "git"
            },
            {
              "lessThan": "814c3b4ea357297c507158bceb07bcdc5fbe9808",
              "status": "affected",
              "version": "e2a7fd22378f6500bcf979edc71e6837271eacfd",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/btrfs/delalloc-space.c",
            "fs/btrfs/space-info.c",
            "fs/btrfs/space-info.h"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "7.1"
            },
            {
              "lessThan": "7.1",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.1.*",
              "status": "unaffected",
              "version": "7.1.5",
              "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": "7.1.5",
                  "versionStartIncluding": "7.1",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.2",
                  "versionStartIncluding": "7.1",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: zoned: fix deadlock waiting for ticket during data relocation\n\nWhen performing data relocation on a zoned filesystem, BTRFS can deadlock\nin handle_reserve_tickets(). The relocation process is waiting on a space\nreservation ticket that can never be fulfilled, because the relocation\nitself is the operation responsible for freeing up that space.\n\nFix this by introducing a new flush state,\nBTRFS_RESERVE_FLUSH_ZONED_RELOCATION, specifically for data chunk\nallocation during zoned relocation. Like\nBTRFS_RESERVE_FLUSH_FREE_SPACE_INODE, this state uses\npriority_reclaim_data_space() instead of the normal flushing path, which\navoids re-entering the relocation code and breaking the deadlock cycle.\n\nIn btrfs_alloc_data_chunk_ondemand(), select this new flush state when the\ninode belongs to a data relocation root on a zoned filesystem."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-17T05:17:09.243Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/f84dbbaa988e1344634a20ddf6c7d51a99f12477"
        },
        {
          "url": "https://git.kernel.org/stable/c/814c3b4ea357297c507158bceb07bcdc5fbe9808"
        }
      ],
      "title": "btrfs: zoned: fix deadlock waiting for ticket during data relocation",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2026-74319",
    "datePublished": "2026-08-15T05:58:16.142Z",
    "dateReserved": "2026-08-15T05:44:03.884Z",
    "dateUpdated": "2026-08-17T05:17:09.243Z",
    "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-W48H-WV4W-HRQ6

CVE-2026-74319 (GCVE-0-2026-74319)

Tags

Sightings

Nomenclature