Vulnerability-Lookup

GHSA-926H-7QF4-C3HQ

Vulnerability from github – Published: 2025-07-25 15:30 – Updated: 2025-12-15 18:30

Details

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

btrfs: fix iteration of extrefs during log replay

At __inode_add_ref() when processing extrefs, if we jump into the next label we have an undefined value of victim_name.len, since we haven't initialized it before we did the goto. This results in an invalid memory access in the next iteration of the loop since victim_name.len was not initialized to the length of the name of the current extref.

Fix this by initializing victim_name.len with the current extref's name length.

Severity

5.5 (Medium)


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

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2025-38382"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-908"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-07-25T13:15:27Z",
    "severity": "MODERATE"
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix iteration of extrefs during log replay\n\nAt __inode_add_ref() when processing extrefs, if we jump into the next\nlabel we have an undefined value of victim_name.len, since we haven\u0027t\ninitialized it before we did the goto. This results in an invalid memory\naccess in the next iteration of the loop since victim_name.len was not\ninitialized to the length of the name of the current extref.\n\nFix this by initializing victim_name.len with the current extref\u0027s name\nlength.",
  "id": "GHSA-926h-7qf4-c3hq",
  "modified": "2025-12-15T18:30:16Z",
  "published": "2025-07-25T15:30:52Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-38382"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/2d11d274e2e1d7c79e2ca8461ce3ff3a95c11171"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/539969fc472886a1d63565459514d47e27fef461"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/54a7081ed168b72a8a2d6ef4ba3a1259705a2926"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/7ac790dc2ba00499a8d671d4a24de4d4ad27e234"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/aee57a0293dca675637e5504709f9f8fd8e871be"
    },
    {
      "type": "WEB",
      "url": "https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    }
  ]
}

CVE-2025-38382 (GCVE-0-2025-38382)

Vulnerability from cvelistv5 – Published: 2025-07-25 12:53 – Updated: 2026-08-05 12:01

Title

btrfs: fix iteration of extrefs during log replay

Summary

In the Linux kernel, the following vulnerability has been resolved: btrfs: fix iteration of extrefs during log replay At __inode_add_ref() when processing extrefs, if we jump into the next label we have an undefined value of victim_name.len, since we haven't initialized it before we did the goto. This results in an invalid memory access in the next iteration of the loop since victim_name.len was not initialized to the length of the name of the current extref. Fix this by initializing victim_name.len with the current extref's name length.

Severity

7.8 (High)


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

Assigner

Linux mitre root

References

6 references

URL	Tags
https://git.kernel.org/stable/c/539969fc472886a1d…
https://git.kernel.org/stable/c/2d11d274e2e1d7c79…
https://git.kernel.org/stable/c/7ac790dc2ba00499a…
https://git.kernel.org/stable/c/aee57a0293dca6756…
https://git.kernel.org/stable/c/54a7081ed168b72a8…
https://lists.debian.org/debian-lts-announce/2025…

Impacted products

2 products

Vendor	Product	Version
Linux	Linux	Affected: 1cf474cd474bc5d3ef63086ffd009a87a5b7bb2e , < 539969fc472886a1d63565459514d47e27fef461 (git) Affected: e43eec81c5167b655b72c781b0e75e62a05e415e , < 2d11d274e2e1d7c79e2ca8461ce3ff3a95c11171 (git) Affected: e43eec81c5167b655b72c781b0e75e62a05e415e , < 7ac790dc2ba00499a8d671d4a24de4d4ad27e234 (git) Affected: e43eec81c5167b655b72c781b0e75e62a05e415e , < aee57a0293dca675637e5504709f9f8fd8e871be (git) Affected: e43eec81c5167b655b72c781b0e75e62a05e415e , < 54a7081ed168b72a8a2d6ef4ba3a1259705a2926 (git) Affected: 6.1.57 , < 6.1.144 (semver)
Linux	Linux	Affected: 6.2 Unaffected: 0 , < 6.2 (semver) Unaffected: 6.1.144 , ≤ 6.1.* (semver) Unaffected: 6.6.97 , ≤ 6.6.* (semver) Unaffected: 6.12.37 , ≤ 6.12.* (semver) Unaffected: 6.15.6 , ≤ 6.15.* (semver) Unaffected: 6.16 , ≤ * (original_commit_for_fix)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2025-11-03T17:37:15.284Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/btrfs/tree-log.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "539969fc472886a1d63565459514d47e27fef461",
              "status": "affected",
              "version": "1cf474cd474bc5d3ef63086ffd009a87a5b7bb2e",
              "versionType": "git"
            },
            {
              "lessThan": "2d11d274e2e1d7c79e2ca8461ce3ff3a95c11171",
              "status": "affected",
              "version": "e43eec81c5167b655b72c781b0e75e62a05e415e",
              "versionType": "git"
            },
            {
              "lessThan": "7ac790dc2ba00499a8d671d4a24de4d4ad27e234",
              "status": "affected",
              "version": "e43eec81c5167b655b72c781b0e75e62a05e415e",
              "versionType": "git"
            },
            {
              "lessThan": "aee57a0293dca675637e5504709f9f8fd8e871be",
              "status": "affected",
              "version": "e43eec81c5167b655b72c781b0e75e62a05e415e",
              "versionType": "git"
            },
            {
              "lessThan": "54a7081ed168b72a8a2d6ef4ba3a1259705a2926",
              "status": "affected",
              "version": "e43eec81c5167b655b72c781b0e75e62a05e415e",
              "versionType": "git"
            },
            {
              "lessThan": "6.1.144",
              "status": "affected",
              "version": "6.1.57",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/btrfs/tree-log.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.2"
            },
            {
              "lessThan": "6.2",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.144",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.97",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.37",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.15.*",
              "status": "unaffected",
              "version": "6.15.6",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.16",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.144",
                  "versionStartIncluding": "6.1.57",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.97",
                  "versionStartIncluding": "6.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.37",
                  "versionStartIncluding": "6.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.15.6",
                  "versionStartIncluding": "6.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.16",
                  "versionStartIncluding": "6.2",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix iteration of extrefs during log replay\n\nAt __inode_add_ref() when processing extrefs, if we jump into the next\nlabel we have an undefined value of victim_name.len, since we haven\u0027t\ninitialized it before we did the goto. This results in an invalid memory\naccess in the next iteration of the loop since victim_name.len was not\ninitialized to the length of the name of the current extref.\n\nFix this by initializing victim_name.len with the current extref\u0027s name\nlength."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The vulnerable code is only reached through tree-log replay during `mount(2)` of a btrfs volume (open_ctree \u2192 btrfs_replay_log \u2192 __add_inode_ref), so the attacker needs local access to present the crafted image via a block device, loop file, or removable media. There is no network-facing path into btrfs log replay.\nAC:L - Triggering is fully deterministic \u2014 the tree-checker\u0027s `check_inode_extref()` never validates the embedded `parent_objectid` against the item\u0027s hash key, so the attacker simply places a mismatching-parent extref first in the item and sets `super_log_root` so replay runs automatically. No race, timing window, or unpredictable memory layout is involved in reaching the invalid access.\nPR:L - btrfs does not set `FS_USERNS_MOUNT`, but an unprivileged session user routinely causes attacker-supplied btrfs media to be mounted by udisks2/systemd automounters on desktops, kiosks, and shared workstations, and image-processing services loop-mount untrusted images on behalf of low-privileged callers. No elevated capability of the attacker\u0027s own is needed in that scenario.\nUI:N - Once the crafted volume is attached, the automounter mounts it and log replay runs unconditionally because `btrfs_super_log_root(disk_super) != 0` is checked with no operator prompt. The attacker performs the mount-triggering action themselves; no separate victim action is required.\nS:U - The out-of-bounds access and the resulting corruption stay within the kernel\u0027s own security authority. No hypervisor, IOMMU, or sandbox boundary is crossed.\nC:H - The uninitialized `victim_name.len` makes `btrfs_get_64()` read past `eb-\u003elen`, and with the accessor\u0027s `ASSERT(check_setget_bounds(...))` compiled out on production kernels, `get_eb_folio_index()` runs off the end of `eb-\u003efolios[]` (index 16 with an attacker-chosen 64K nodesize on 4K pages), turning adjacent slab contents into a `struct folio *` that `folio_address()` dereferences \u2014 an unbounded wild kernel read, not a few-byte bounded one.\nI:H - The out-of-bounds and uninitialized data is interpreted as inode backref metadata and then acted upon: `read_one_inode()` on a garbage `parent_objectid`, `inc_nlink()` on the inode, and `unlink_inode_for_log_replay()` removing directory entries, so kernel memory read out of bounds directly drives modification of filesystem state. Combined with the wild-pointer arithmetic on `eb-\u003efolios[]`, this is memory corruption that must be treated as leverageable for control-flow influence.\nA:H - In the common configurations the bogus folio index yields a NULL or wild `folio_address()` dereference during mount, producing a kernel oops, and with `CONFIG_BTRFS_ASSERT=y` the bounds assertion calls `BUG()` outright. Either outcome is a kernel crash in the mount path."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T12:01:29.887Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/539969fc472886a1d63565459514d47e27fef461"
        },
        {
          "url": "https://git.kernel.org/stable/c/2d11d274e2e1d7c79e2ca8461ce3ff3a95c11171"
        },
        {
          "url": "https://git.kernel.org/stable/c/7ac790dc2ba00499a8d671d4a24de4d4ad27e234"
        },
        {
          "url": "https://git.kernel.org/stable/c/aee57a0293dca675637e5504709f9f8fd8e871be"
        },
        {
          "url": "https://git.kernel.org/stable/c/54a7081ed168b72a8a2d6ef4ba3a1259705a2926"
        }
      ],
      "title": "btrfs: fix iteration of extrefs during log replay",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-38382",
    "datePublished": "2025-07-25T12:53:23.665Z",
    "dateReserved": "2025-04-16T04:51:24.010Z",
    "dateUpdated": "2026-08-05T12:01:29.887Z",
    "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.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.