CVE-2025-38028 (GCVE-0-2025-38028)

Vulnerability from cvelistv5 – Published: 2025-06-18 09:28 – Updated: 2026-08-05 11:59
VLAI
Title
NFS/localio: Fix a race in nfs_local_open_fh()
Summary
In the Linux kernel, the following vulnerability has been resolved: NFS/localio: Fix a race in nfs_local_open_fh() Once the clp->cl_uuid.lock has been dropped, another CPU could come in and free the struct nfsd_file that was just added. To prevent that from happening, take the RCU read lock before dropping the spin lock.
Assigner
Linux CNA
Impacted products
Vendor Product Version
Linux Linux Affected: 86e00412254a717ffd5d38dc5ec0ee1cce6281b3 , < 185a2f2ddabdcf999823f61de67f86376883920d (git)
Affected: 86e00412254a717ffd5d38dc5ec0ee1cce6281b3 , < fa7ab64f1e2fdc8f2603aab8e0dd20de89cb10d9 (git)
Create a notification for this product.
Linux Linux Affected: 6.14
Unaffected: 0 , < 6.14 (semver)
Unaffected: 6.14.8 , ≤ 6.14.* (semver)
Unaffected: 6.15 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/nfs/localio.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "185a2f2ddabdcf999823f61de67f86376883920d",
              "status": "affected",
              "version": "86e00412254a717ffd5d38dc5ec0ee1cce6281b3",
              "versionType": "git"
            },
            {
              "lessThan": "fa7ab64f1e2fdc8f2603aab8e0dd20de89cb10d9",
              "status": "affected",
              "version": "86e00412254a717ffd5d38dc5ec0ee1cce6281b3",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/nfs/localio.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.14"
            },
            {
              "lessThan": "6.14",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.14.*",
              "status": "unaffected",
              "version": "6.14.8",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.15",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.14.8",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.15",
                  "versionStartIncluding": "6.14",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nNFS/localio: Fix a race in nfs_local_open_fh()\n\nOnce the clp-\u003ecl_uuid.lock has been dropped, another CPU could come in\nand free the struct nfsd_file that was just added. To prevent that from\nhappening, take the RCU read lock before dropping the spin lock."
        }
      ],
      "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 the NFS client LOCALIO fast path, reached by ordinary read/write/commit syscalls against a mounted NFS filesystem (nfs_generic_pg_pgios and nfs_initiate_commit both call nfs_local_open_fh). LOCALIO by definition requires the nfsd server to be on the same host, so there is no remote packet path to this code.\nAC:L - The attacker controls both sides of the race: one set of threads issues concurrent I/O to enter nfs_local_open_fh, while another forces nfs_localio_disable_client()/nfs_uuid_put() to free the cached nfsd_file (via -ENOMEM/-ENXIO/-ENOENT from __nfs_local_open_fh or -EAGAIN from nfs_local_doio). The window is repeatedly retriable at will and widened by preemption under CPU pressure.\nPR:L - Any unprivileged local user with access to files on a LOCALIO-enabled NFS mount can drive both sides purely with read/write/close syscalls; no capability check exists anywhere along nfs_generic_pg_pgios \u2192 nfs_local_open_fh. The mount itself is a deployment precondition rather than a privilege the attacker must hold.\nUI:N - The attacker triggers the race entirely from their own concurrent threads; no victim action is needed once the localio mount exists.\nS:U - The use-after-free corrupts kernel slab memory within the same kernel security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - If the freed nfsd_file slot is reallocated, nfs_local_open_fh returns a pointer to a different live nfsd_file whose nf_file is then used for the NFS read, disclosing the contents of an unrelated file on the exported filesystem; more generally a UAF on the slab yields an arbitrary-read primitive.\nI:H - refcount_inc_not_zero() writes into freed/reallocated memory, and the returned stale nfsd_file is used for write_iter, corrupting a different file\u0027s data as well as another object\u0027s refcount, which enables a follow-on premature free and control-flow hijack.\nA:H - Use-after-free on the nfsd_file slab causes refcount warnings, slab corruption and oops/panic, and the corrupted refcount leads to a second premature free of a live nfsd_file \u2014 a repeatable local denial of service."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:59:03.121Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/185a2f2ddabdcf999823f61de67f86376883920d"
        },
        {
          "url": "https://git.kernel.org/stable/c/fa7ab64f1e2fdc8f2603aab8e0dd20de89cb10d9"
        }
      ],
      "title": "NFS/localio: Fix a race in nfs_local_open_fh()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2025-38028",
    "datePublished": "2025-06-18T09:28:33.184Z",
    "dateReserved": "2025-04-16T04:51:23.978Z",
    "dateUpdated": "2026-08-05T11:59:03.121Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2025-38028",
      "date": "2026-11-19",
      "epss": "0.00128",
      "percentile": "0.02555"
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-05T14:38:55+00:00",
      "cve": "CVE-2025-38028",
      "id": "CVE-2025-38028",
      "initial_release_date": "2025-06-18T00:00:00+00:00",
      "product_status:known_affected": "1",
      "product_status:known_not_affected": "199",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: Linux kernel: Privilege escalation via race condition in NFS/localio",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-38028.json",
      "version": "3"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    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.