CVE-2024-50241 (GCVE-0-2024-50241)

Vulnerability from cvelistv5 – Published: 2024-11-09 10:14 – Updated: 2026-08-05 11:42
VLAI
Title
NFSD: Initialize struct nfsd4_copy earlier
Summary
In the Linux kernel, the following vulnerability has been resolved: NFSD: Initialize struct nfsd4_copy earlier Ensure the refcount and async_copies fields are initialized early. cleanup_async_copy() will reference these fields if an error occurs in nfsd4_copy(). If they are not correctly initialized, at the very least, a refcount underflow occurs.
Assigner
Linux CNA
Impacted products
Vendor Product Version
Linux Linux Affected: 9e52ff544e0bfa09ee339fd7b0937ee3c080c24e , < 059434d23c4578d9d02efb92d848ea21bc640112 (git)
Affected: 43e46ee5efc03990b223f7aa8b77aa9c3d3acfdf , < 7267625baf365a969f1b25ded6f07b64bc90ec5b (git)
Affected: 7ea9260874b779637aff6d24c344b8ef4ac862a0 , < c3074003fa6837c2b89a34d8d12d9463b59d22d6 (git)
Affected: ae267989b7b7933dfedcd26468d0a88fc3a9da9e , < 421f1a2a1afb47d88de09457ef7687e1df7bc997 (git)
Affected: 6a488ad7745b8f64625c6d3a24ce7e448e83f11b , < e30a9a2f69c34a00a3cb4fd45c5d231929e66fb1 (git)
Affected: aadc3bbea163b6caaaebfdd2b6c4667fbc726752 , < 63fab04cbd0f96191b6e5beedc3b643b01c15889 (git)
Affected: b4e21431a0db4854b5023cd5af001be557e6c3db (git)
Affected: 6.10.14 , < 6.11 (semver)
Create a notification for this product.
Linux Linux Affected: 6.11.3 , < 6.11.7 (semver)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/nfsd/nfs4proc.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "059434d23c4578d9d02efb92d848ea21bc640112",
              "status": "affected",
              "version": "9e52ff544e0bfa09ee339fd7b0937ee3c080c24e",
              "versionType": "git"
            },
            {
              "lessThan": "7267625baf365a969f1b25ded6f07b64bc90ec5b",
              "status": "affected",
              "version": "43e46ee5efc03990b223f7aa8b77aa9c3d3acfdf",
              "versionType": "git"
            },
            {
              "lessThan": "c3074003fa6837c2b89a34d8d12d9463b59d22d6",
              "status": "affected",
              "version": "7ea9260874b779637aff6d24c344b8ef4ac862a0",
              "versionType": "git"
            },
            {
              "lessThan": "421f1a2a1afb47d88de09457ef7687e1df7bc997",
              "status": "affected",
              "version": "ae267989b7b7933dfedcd26468d0a88fc3a9da9e",
              "versionType": "git"
            },
            {
              "lessThan": "e30a9a2f69c34a00a3cb4fd45c5d231929e66fb1",
              "status": "affected",
              "version": "6a488ad7745b8f64625c6d3a24ce7e448e83f11b",
              "versionType": "git"
            },
            {
              "lessThan": "63fab04cbd0f96191b6e5beedc3b643b01c15889",
              "status": "affected",
              "version": "aadc3bbea163b6caaaebfdd2b6c4667fbc726752",
              "versionType": "git"
            },
            {
              "status": "affected",
              "version": "b4e21431a0db4854b5023cd5af001be557e6c3db",
              "versionType": "git"
            },
            {
              "lessThan": "6.11",
              "status": "affected",
              "version": "6.10.14",
              "versionType": "semver"
            }
          ]
        },
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/nfsd/nfs4proc.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "6.11.7",
              "status": "affected",
              "version": "6.11.3",
              "versionType": "semver"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.11.7",
                  "versionStartIncluding": "6.11.3",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionStartIncluding": "6.10.14",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nNFSD: Initialize struct nfsd4_copy earlier\n\nEnsure the refcount and async_copies fields are initialized early.\ncleanup_async_copy() will reference these fields if an error occurs\nin nfsd4_copy(). If they are not correctly initialized, at the very\nleast, a refcount underflow occurs."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:N - The flaw is in nfsd\u0027s NFSv4.2 `OP_COPY` handler (`fs/nfsd/nfs4proc.c:nfsd4_copy()`), reached purely by sending a COMPOUND over TCP/2049 from a remote NFS client. The `ca_synchronous` flag that selects the vulnerable async branch is decoded directly from the wire in `nfsd4_decode_copy()`.\nAC:L - The attacker fully controls both trigger conditions \u2014 setting `ca_synchronous=false` and issuing more concurrent async COPYs than `sp_nrthreads` (default 8) by first parking several long-running copies. There is no race outside the attacker\u0027s control, no memory-layout dependency, and no unusual kernel configuration needed for the intra-server path.\nPR:N - Under AUTH_SYS \u2014 the default and overwhelmingly common NFS configuration \u2014 the server verifies no secret; a client simply asserts a UID to complete EXCHANGE_ID/CREATE_SESSION and OPEN the source/destination files, so no credentials in the CVSS sense are required. This matches the PR:N assigned to CVE-2024-53073, the companion fix to the identical error path.\nUI:N - The attacker\u0027s own COPY requests drive the entire sequence; no administrator or user on the NFS server has to open a file, mount anything, or take any action.\nS:U - The refcount underflow and leaked allocation are confined to the NFS server kernel\u0027s own memory and security authority, with no crossing into a hypervisor, IOMMU, or sandbox boundary.\nC:N - The underflow is caught by `refcount_warn_saturate()` and the object is simply never freed \u2014 there is no out-of-bounds read, no use-after-free of live data, and nothing from kernel memory is returned to the requesting client.\nI:N - No attacker-controlled write occurs: the leaked `struct nfsd4_copy` is unreachable and its refcount is saturated, so it is never reused or freed, yielding no corruption or control-flow primitive.\nA:H - `WARN_ONCE(\"refcount_t: underflow; use-after-free\")` panics the server outright on the common hardened/cloud setting `panic_on_warn=1`, and absent that, every triggering request permanently leaks a ~0.5 KB slab object, giving an unauthenticated remote client an unbounded kernel memory-exhaustion primitive that drives the NFS server to OOM."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:42:42.206Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/059434d23c4578d9d02efb92d848ea21bc640112"
        },
        {
          "url": "https://git.kernel.org/stable/c/7267625baf365a969f1b25ded6f07b64bc90ec5b"
        },
        {
          "url": "https://git.kernel.org/stable/c/c3074003fa6837c2b89a34d8d12d9463b59d22d6"
        },
        {
          "url": "https://git.kernel.org/stable/c/421f1a2a1afb47d88de09457ef7687e1df7bc997"
        },
        {
          "url": "https://git.kernel.org/stable/c/e30a9a2f69c34a00a3cb4fd45c5d231929e66fb1"
        },
        {
          "url": "https://git.kernel.org/stable/c/63fab04cbd0f96191b6e5beedc3b643b01c15889"
        }
      ],
      "title": "NFSD: Initialize struct nfsd4_copy earlier",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-50241",
    "datePublished": "2024-11-09T10:14:51.119Z",
    "dateReserved": "2024-10-21T19:36:19.976Z",
    "dateUpdated": "2026-08-05T11:42:42.206Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-50241",
      "date": "2026-11-19",
      "epss": "0.00478",
      "percentile": "0.42075"
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-05T13:47:45+00:00",
      "cve": "CVE-2024-50241",
      "id": "CVE-2024-50241",
      "initial_release_date": "2024-11-09T00:00:00+00:00",
      "product_status:known_affected": "42",
      "product_status:known_not_affected": "157",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: NFSD: Initialize struct nfsd4_copy earlier",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-50241.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.