FKIE_CVE-2026-99694

Vulnerability from fkie_nvd - Published: 2026-11-20 06:18 - Updated: 2026-11-20 06:18
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved: ocfs2: do not index before the entry array when dividing an empty bucket ocfs2_divide_xattr_bucket() appends an empty bucket carrying a sentinel hash when the source bucket has no divide position, taking that hash from xh_entries[start - 1]. ocfs2_xattr_find_divide_pos() returns count when every entry shares one hash, and its loop does not run at all for count < 2, so an empty bucket comes back with start == count == 0 and the read is xh_entries[-1]. That is outside the __counted_by_le(xh_count) bounds of xh_entries[] and lands on the header, so the value picked up is xh_count | xh_free_start << 16. One above it is written into the new bucket's xh_entries[0] and committed, which leaves a bucket whose first hash does not follow the bucket before it. ocfs2_xattr_bucket_find() binary searches on xh_entries[0], so the broken key hides the range the sentinel was meant to cover: getxattr() answers -ENODATA for an attribute that is stored, and an insert can go to the wrong bucket and leave two copies of a name. The cross cluster divide hands the same value back as a tree record's e_cpos, which then claims a hash range it does not cover. Read xh_entries[0] instead. The branch is only reached when every entry shares one hash, so for a non-empty bucket it holds the same value, and for an empty one it is the slot that carries the bucket key. An empty bucket reaches the divide from ocfs2_check_xattr_bucket_collision(), which reports no collision for one, through ocfs2_add_new_xattr_bucket() and ocfs2_extend_xattr_bucket(). It does not take a failed set to get there: a divide that finds no position is itself what leaves an empty sentinel bucket behind, and a later extend can pick it as the target.
Impacted products
Vendor Product Version

{
  "affected": [
    {
      "affectedData": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/ocfs2/xattr.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "58308e76c036822c78947efbbdcb800c1df6f6b2",
              "status": "affected",
              "version": "80bcaf3469b8aefd316d4ceb27d9af7cfbb0b913",
              "versionType": "git"
            },
            {
              "lessThan": "7148fa383fb000d3125989ff3e63f3458a33591d",
              "status": "affected",
              "version": "80bcaf3469b8aefd316d4ceb27d9af7cfbb0b913",
              "versionType": "git"
            },
            {
              "lessThan": "b710975d07b049c957ba6b93985b1cf9b169ad6e",
              "status": "affected",
              "version": "80bcaf3469b8aefd316d4ceb27d9af7cfbb0b913",
              "versionType": "git"
            },
            {
              "lessThan": "7133a0d0954c109f1764ebf8ab32d7e757a6c587",
              "status": "affected",
              "version": "80bcaf3469b8aefd316d4ceb27d9af7cfbb0b913",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/ocfs2/xattr.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "2.6.28"
            },
            {
              "lessThan": "2.6.28",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.118",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.18.*",
              "status": "unaffected",
              "version": "6.18.64",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "7.3.*",
              "status": "unaffected",
              "version": "7.3.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "7.4-rc2",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nocfs2: do not index before the entry array when dividing an empty bucket\n\nocfs2_divide_xattr_bucket() appends an empty bucket carrying a sentinel\nhash when the source bucket has no divide position, taking that hash\nfrom xh_entries[start - 1].  ocfs2_xattr_find_divide_pos() returns count\nwhen every entry shares one hash, and its loop does not run at all for\ncount \u003c 2, so an empty bucket comes back with start == count == 0 and\nthe read is xh_entries[-1].\n\nThat is outside the __counted_by_le(xh_count) bounds of xh_entries[] and\nlands on the header, so the value picked up is\nxh_count | xh_free_start \u003c\u003c 16.  One above it is written into the new\nbucket\u0027s xh_entries[0] and committed, which leaves a bucket whose first\nhash does not follow the bucket before it.  ocfs2_xattr_bucket_find()\nbinary searches on xh_entries[0], so the broken key hides the range the\nsentinel was meant to cover: getxattr() answers -ENODATA for an\nattribute that is stored, and an insert can go to the wrong bucket and\nleave two copies of a name.  The cross cluster divide hands the same\nvalue back as a tree record\u0027s e_cpos, which then claims a hash range it\ndoes not cover.\n\nRead xh_entries[0] instead.  The branch is only reached when every entry\nshares one hash, so for a non-empty bucket it holds the same value, and\nfor an empty one it is the slot that carries the bucket key.\n\nAn empty bucket reaches the divide from\nocfs2_check_xattr_bucket_collision(), which reports no collision for\none, through ocfs2_add_new_xattr_bucket() and\nocfs2_extend_xattr_bucket().  It does not take a failed set to get\nthere: a divide that finds no position is itself what leaves an empty\nsentinel bucket behind, and a later extend can pick it as the target."
    }
  ],
  "id": "CVE-2026-99694",
  "lastModified": "2026-11-20T06:18:04.710",
  "metrics": {},
  "published": "2026-11-20T06:18:04.710",
  "references": [
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/58308e76c036822c78947efbbdcb800c1df6f6b2"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/7133a0d0954c109f1764ebf8ab32d7e757a6c587"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/7148fa383fb000d3125989ff3e63f3458a33591d"
    },
    {
      "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "url": "https://git.kernel.org/stable/c/b710975d07b049c957ba6b93985b1cf9b169ad6e"
    }
  ],
  "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
  "vulnStatus": "Received"
}



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.