CVE-2024-50087 (GCVE-0-2024-50087)
Vulnerability from cvelistv5
Published
2024-10-29 00:50
Modified
2026-08-05 11:41
Severity ?
7.8 (High) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Summary
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix uninitialized pointer free on read_alloc_one_name() error The function read_alloc_one_name() does not initialize the name field of the passed fscrypt_str struct if kmalloc fails to allocate the corresponding buffer. Thus, it is not guaranteed that fscrypt_str.name is initialized when freeing it. This is a follow-up to the linked patch that fixes the remaining instances of the bug introduced by commit e43eec81c516 ("btrfs: use struct qstr instead of name and namelen pairs").
References
Impacted products
Vendor Product Version
Linux Linux Version: 1cf474cd474bc5d3ef63086ffd009a87a5b7bb2e
Version: e43eec81c5167b655b72c781b0e75e62a05e415e
Version: e43eec81c5167b655b72c781b0e75e62a05e415e
Version: e43eec81c5167b655b72c781b0e75e62a05e415e
Version: 6.1.57   ≤
Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "LOCAL",
              "availabilityImpact": "HIGH",
              "baseScore": 5.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2024-50087",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2025-10-01T20:23:12.303362Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "cweId": "CWE-824",
                "description": "CWE-824 Access of Uninitialized Pointer",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2025-10-01T20:27:20.200Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2025-11-03T22:25:20.291Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.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": "b37de9491f140a0ff125c27dd1050185c3accbc1",
              "status": "affected",
              "version": "1cf474cd474bc5d3ef63086ffd009a87a5b7bb2e",
              "versionType": "git"
            },
            {
              "lessThan": "7fc7c47b9ba0cf2d192f2117a64b24881b0b577f",
              "status": "affected",
              "version": "e43eec81c5167b655b72c781b0e75e62a05e415e",
              "versionType": "git"
            },
            {
              "lessThan": "1ec28de5e476913ae51f909660b4447eddb28838",
              "status": "affected",
              "version": "e43eec81c5167b655b72c781b0e75e62a05e415e",
              "versionType": "git"
            },
            {
              "lessThan": "2ab5e243c2266c841e0f6904fad1514b18eaf510",
              "status": "affected",
              "version": "e43eec81c5167b655b72c781b0e75e62a05e415e",
              "versionType": "git"
            },
            {
              "lessThan": "6.1.114",
              "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.114",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.58",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.11.*",
              "status": "unaffected",
              "version": "6.11.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.12",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.114",
                  "versionStartIncluding": "6.1.57",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.58",
                  "versionStartIncluding": "6.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.11.5",
                  "versionStartIncluding": "6.2",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12",
                  "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 uninitialized pointer free on read_alloc_one_name() error\n\nThe function read_alloc_one_name() does not initialize the name field of\nthe passed fscrypt_str struct if kmalloc fails to allocate the\ncorresponding buffer.  Thus, it is not guaranteed that\nfscrypt_str.name is initialized when freeing it.\n\nThis is a follow-up to the linked patch that fixes the remaining\ninstances of the bug introduced by commit e43eec81c516 (\"btrfs: use\nstruct qstr instead of name and namelen pairs\")."
        }
      ],
      "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 executes only in the btrfs mount-time log-replay path (`btrfs_replay_log()` \u2192 `replay_one_buffer()`/`replay_dir_deletes()`), reached through the local `mount()` syscall on a local block device or loop image. There is no remote or adjacent-network path into tree-log replay.\nAC:L - The attacker supplies the image, so log replay is guaranteed to run and can be padded with thousands of dir-index entries, each producing another `kmalloc(GFP_NOFS)` attempt; the required allocation failure is induced by attacker-generated memory pressure (userspace ballooning, or a memcg-constrained mount context), which is within the attacker\u0027s influence rather than beyond it.\nPR:L - In the most severe realistic deployment \u2014 desktops and kiosks running udisks2/removable-media automount, which supports btrfs \u2014 an unprivileged local user mounts an attacker-prepared btrfs volume with a dirty log without holding root, and the concurrent memory-pressure side needs no privileges at all.\nUI:N - The attacker performs the triggering mount themselves via automount of attacker-controlled removable media or a mount helper; no separate victim has to open a file or take any action.\nS:U - The corruption occurs in kernel slab memory during mount and stays entirely within the kernel\u0027s own security authority, with no crossing of a hypervisor, IOMMU, or sandbox boundary.\nC:H - `kfree()` on an uninitialized stack value can release a still-live slab object whose stale pointer was left by earlier frames in the same mount call chain, yielding a use-after-free that can be reallocated with attacker-chosen data and read back, exposing arbitrary kernel memory.\nI:H - The arbitrary/premature free gives a classic heap-corruption primitive \u2014 reclaiming the freed object with a sprayed structure permits attacker-controlled writes into kernel objects and potential control-flow hijack.\nA:H - Freeing a wild pointer typically faults inside the allocator or trips slab consistency checks, and the resulting use-after-free corrupts kernel state during mount, producing an oops or panic."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:41:32.766Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/b37de9491f140a0ff125c27dd1050185c3accbc1"
        },
        {
          "url": "https://git.kernel.org/stable/c/7fc7c47b9ba0cf2d192f2117a64b24881b0b577f"
        },
        {
          "url": "https://git.kernel.org/stable/c/1ec28de5e476913ae51f909660b4447eddb28838"
        },
        {
          "url": "https://git.kernel.org/stable/c/2ab5e243c2266c841e0f6904fad1514b18eaf510"
        }
      ],
      "title": "btrfs: fix uninitialized pointer free on read_alloc_one_name() error",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-50087",
    "datePublished": "2024-10-29T00:50:30.313Z",
    "dateReserved": "2024-10-21T19:36:19.942Z",
    "dateUpdated": "2026-08-05T11:41:32.766Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html\"}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2025-11-03T22:25:20.291Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 5.5, \"attackVector\": \"LOCAL\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"HIGH\", \"privilegesRequired\": \"LOW\", \"confidentialityImpact\": \"NONE\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-50087\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2025-10-01T20:23:12.303362Z\"}}}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-824\", \"description\": \"CWE-824 Access of Uninitialized Pointer\"}]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2025-10-01T15:13:48.548Z\"}}], \"cna\": {\"title\": \"btrfs: fix uninitialized pointer free on read_alloc_one_name() error\", \"metrics\": [{\"cvssV3_1\": {\"version\": \"3.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\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"AV:L - The vulnerable code executes only in the btrfs mount-time log-replay path (`btrfs_replay_log()` \\u2192 `replay_one_buffer()`/`replay_dir_deletes()`), reached through the local `mount()` syscall on a local block device or loop image. There is no remote or adjacent-network path into tree-log replay.\\nAC:L - The attacker supplies the image, so log replay is guaranteed to run and can be padded with thousands of dir-index entries, each producing another `kmalloc(GFP_NOFS)` attempt; the required allocation failure is induced by attacker-generated memory pressure (userspace ballooning, or a memcg-constrained mount context), which is within the attacker\u0027s influence rather than beyond it.\\nPR:L - In the most severe realistic deployment \\u2014 desktops and kiosks running udisks2/removable-media automount, which supports btrfs \\u2014 an unprivileged local user mounts an attacker-prepared btrfs volume with a dirty log without holding root, and the concurrent memory-pressure side needs no privileges at all.\\nUI:N - The attacker performs the triggering mount themselves via automount of attacker-controlled removable media or a mount helper; no separate victim has to open a file or take any action.\\nS:U - The corruption occurs in kernel slab memory during mount and stays entirely within the kernel\u0027s own security authority, with no crossing of a hypervisor, IOMMU, or sandbox boundary.\\nC:H - `kfree()` on an uninitialized stack value can release a still-live slab object whose stale pointer was left by earlier frames in the same mount call chain, yielding a use-after-free that can be reallocated with attacker-chosen data and read back, exposing arbitrary kernel memory.\\nI:H - The arbitrary/premature free gives a classic heap-corruption primitive \\u2014 reclaiming the freed object with a sprayed structure permits attacker-controlled writes into kernel objects and potential control-flow hijack.\\nA:H - Freeing a wild pointer typically faults inside the allocator or trips slab consistency checks, and the resulting use-after-free corrupts kernel state during mount, producing an oops or panic.\"}]}], \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"1cf474cd474bc5d3ef63086ffd009a87a5b7bb2e\", \"lessThan\": \"b37de9491f140a0ff125c27dd1050185c3accbc1\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"e43eec81c5167b655b72c781b0e75e62a05e415e\", \"lessThan\": \"7fc7c47b9ba0cf2d192f2117a64b24881b0b577f\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"e43eec81c5167b655b72c781b0e75e62a05e415e\", \"lessThan\": \"1ec28de5e476913ae51f909660b4447eddb28838\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"e43eec81c5167b655b72c781b0e75e62a05e415e\", \"lessThan\": \"2ab5e243c2266c841e0f6904fad1514b18eaf510\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"6.1.57\", \"lessThan\": \"6.1.114\", \"versionType\": \"semver\"}], \"programFiles\": [\"fs/btrfs/tree-log.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"6.2\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"6.2\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"6.1.114\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.1.*\"}, {\"status\": \"unaffected\", \"version\": \"6.6.58\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.6.*\"}, {\"status\": \"unaffected\", \"version\": \"6.11.5\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.11.*\"}, {\"status\": \"unaffected\", \"version\": \"6.12\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"fs/btrfs/tree-log.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/b37de9491f140a0ff125c27dd1050185c3accbc1\"}, {\"url\": \"https://git.kernel.org/stable/c/7fc7c47b9ba0cf2d192f2117a64b24881b0b577f\"}, {\"url\": \"https://git.kernel.org/stable/c/1ec28de5e476913ae51f909660b4447eddb28838\"}, {\"url\": \"https://git.kernel.org/stable/c/2ab5e243c2266c841e0f6904fad1514b18eaf510\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nbtrfs: fix uninitialized pointer free on read_alloc_one_name() error\\n\\nThe function read_alloc_one_name() does not initialize the name field of\\nthe passed fscrypt_str struct if kmalloc fails to allocate the\\ncorresponding buffer.  Thus, it is not guaranteed that\\nfscrypt_str.name is initialized when freeing it.\\n\\nThis is a follow-up to the linked patch that fixes the remaining\\ninstances of the bug introduced by commit e43eec81c516 (\\\"btrfs: use\\nstruct qstr instead of name and namelen pairs\\\").\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.1.114\", \"versionStartIncluding\": \"6.1.57\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.6.58\", \"versionStartIncluding\": \"6.2\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.11.5\", \"versionStartIncluding\": \"6.2\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.12\", \"versionStartIncluding\": \"6.2\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2026-08-05T11:41:32.766Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-50087\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-08-05T11:41:32.766Z\", \"dateReserved\": \"2024-10-21T19:36:19.942Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-10-29T00:50:30.313Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.