CVE-2024-50248 (GCVE-0-2024-50248)

Vulnerability from cvelistv5 – Published: 2024-11-09 10:14 – Updated: 2026-08-05 11:42
VLAI
Title
ntfs3: Add bounds checking to mi_enum_attr()
Summary
In the Linux kernel, the following vulnerability has been resolved: ntfs3: Add bounds checking to mi_enum_attr() Added bounds checking to make sure that every attr don't stray beyond valid memory region.
Assigner
Linux CNA
Impacted products
Vendor Product Version
Linux Linux Affected: 4534a70b7056fd4b9a1c6db5a4ce3c98546b291e , < 386613a44b858304a88529ade2ccc1e079a5fc56 (git)
Affected: 4534a70b7056fd4b9a1c6db5a4ce3c98546b291e , < 22cdf3be7d34f61a91b9e2966fec3a29f3871398 (git)
Affected: 4534a70b7056fd4b9a1c6db5a4ce3c98546b291e , < 809f9b419c75f8042c58434d2bfe849140643e9d (git)
Affected: 4534a70b7056fd4b9a1c6db5a4ce3c98546b291e , < 556bdf27c2dd5c74a9caacbe524b943a6cd42d99 (git)
Create a notification for this product.
Linux Linux Affected: 5.15
Unaffected: 0 , < 5.15 (semver)
Unaffected: 6.1.120 , ≤ 6.1.* (semver)
Unaffected: 6.6.60 , ≤ 6.6.* (semver)
Unaffected: 6.11.7 , ≤ 6.11.* (semver)
Unaffected: 6.12 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2025-11-03T20:44:37.543Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/ntfs3/record.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "386613a44b858304a88529ade2ccc1e079a5fc56",
              "status": "affected",
              "version": "4534a70b7056fd4b9a1c6db5a4ce3c98546b291e",
              "versionType": "git"
            },
            {
              "lessThan": "22cdf3be7d34f61a91b9e2966fec3a29f3871398",
              "status": "affected",
              "version": "4534a70b7056fd4b9a1c6db5a4ce3c98546b291e",
              "versionType": "git"
            },
            {
              "lessThan": "809f9b419c75f8042c58434d2bfe849140643e9d",
              "status": "affected",
              "version": "4534a70b7056fd4b9a1c6db5a4ce3c98546b291e",
              "versionType": "git"
            },
            {
              "lessThan": "556bdf27c2dd5c74a9caacbe524b943a6cd42d99",
              "status": "affected",
              "version": "4534a70b7056fd4b9a1c6db5a4ce3c98546b291e",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/ntfs3/record.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.15"
            },
            {
              "lessThan": "5.15",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.120",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.60",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.11.*",
              "status": "unaffected",
              "version": "6.11.7",
              "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.120",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.60",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.11.7",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12",
                  "versionStartIncluding": "5.15",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nntfs3: Add bounds checking to mi_enum_attr()\n\nAdded bounds checking to make sure that every attr don\u0027t stray beyond\nvalid memory region."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.1,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The vulnerability is triggered by parsing attacker-crafted MFT records from an NTFS volume, which requires the image to be mounted on the local system (loop device, USB stick, or automounted removable media). There is no network-facing path into `mi_enum_attr()`.\nAC:L - The attacker fully controls every field involved (`rec-\u003eattr_off`, `rec-\u003eused`, `rec-\u003etotal`, `attr-\u003esize`) and the overread is deterministic on the first attribute enumeration \u2014 no race, timing window, or uncontrolled memory-layout condition is involved.\nPR:L - An unprivileged local user can get an arbitrary NTFS image mounted on common desktop/kiosk configurations via udisks2/systemd automount of removable media, or via `user`-option/loop mounts; no root in the initial namespace is needed for the realistic scenario.\nUI:N - In the highest-impact scenario the attacker supplies and mounts the malicious volume themselves (inserting media that is auto-mounted, or loop-mounting their own image), so no action by a separate victim is required.\nS:U - The out-of-bounds access stays within the kernel\u0027s own memory and security authority; no VM, IOMMU, or sandbox boundary is crossed.\nC:H - `attr-\u003esize` is dereferenced at an attacker-influenced offset beyond the `kmalloc()`ed MFT record buffer, reading adjacent kernel heap contents; the commit\u0027s own framing is that attributes could \"stray beyond valid memory region\", so the read is not reliably bounded.\nI:N - The defect is purely a read of `attr-\u003esize`; the surviving `off + asize \u003e used` boundary test still constrains any attribute handed back to callers, so no out-of-bounds write or control-flow corruption primitive arises.\nA:H - The out-of-bounds dereference can hit an unmapped page or trip KASAN/hardened-allocator checks, producing a kernel oops or panic and denying service to the whole system."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T11:42:45.435Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/386613a44b858304a88529ade2ccc1e079a5fc56"
        },
        {
          "url": "https://git.kernel.org/stable/c/22cdf3be7d34f61a91b9e2966fec3a29f3871398"
        },
        {
          "url": "https://git.kernel.org/stable/c/809f9b419c75f8042c58434d2bfe849140643e9d"
        },
        {
          "url": "https://git.kernel.org/stable/c/556bdf27c2dd5c74a9caacbe524b943a6cd42d99"
        }
      ],
      "title": "ntfs3: Add bounds checking to mi_enum_attr()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-50248",
    "datePublished": "2024-11-09T10:14:56.965Z",
    "dateReserved": "2024-10-21T19:36:19.978Z",
    "dateUpdated": "2026-08-05T11:42:45.435Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-50248",
      "date": "2026-11-19",
      "epss": "0.0022",
      "percentile": "0.12726"
    },
    "microsoft_vex": {
      "current_release_date": "2026-08-12T23:28:23.000Z",
      "cve": "CVE-2024-50248",
      "id": "msrc_CVE-2024-50248",
      "initial_release_date": "2025-01-29T00:00:00.000Z",
      "product_status:fixed": "2",
      "product_status:known_affected": "2",
      "product_status:under_investigation": "5",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "ntfs3: Add bounds checking to mi_enum_attr()",
      "url": "https://msrc.microsoft.com/csaf/vex/2025/msrc_cve-2024-50248.json",
      "version": "5"
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-05T13:48:02+00:00",
      "cve": "CVE-2024-50248",
      "id": "CVE-2024-50248",
      "initial_release_date": "2024-11-09T00:00:00+00:00",
      "product_status:known_not_affected": "199",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: ntfs3: Add bounds checking to mi_enum_attr()",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2024/cve-2024-50248.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.