GHSA-PP64-V6P6-8MV7

Vulnerability from github – Published: 2026-11-19 15:31 – Updated: 2026-11-19 15:31
VLAI
Details

In the Linux kernel, the following vulnerability has been resolved:

xfs: reject out-of-range attribute value lengths in xfs_attr_copy_value

xfs_attr_copy_value() takes the value length as a signed int and, for a remote xattr, is handed args->rmtvaluelen. That field is filled from the on-disk __be32 xfs_attr_leaf_name_remote.valuelen in xfs_attr3_leaf_getvalue(), so a crafted length such as 0x80000000 is stored into the signed rmtvaluelen as a negative number.

The "buffer too small" guard in xfs_attr_copy_value() is a signed comparison:

if (args->valuelen < valuelen)
    return -ERANGE;

A negative valuelen therefore compares as smaller than the caller's buffer size, skips the -ERANGE path, and is then used as a copy length, leading to an out-of-bounds copy of a full remote block into a small getxattr(2) buffer on a mounted crafted image.

Reject a value length that is negative or larger than the maximum xattr size before it is used, so a bogus on-disk length can no longer slip through the value copier.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-99400"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-11-19T15:17:52Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nxfs: reject out-of-range attribute value lengths in xfs_attr_copy_value\n\nxfs_attr_copy_value() takes the value length as a signed int and, for a\nremote xattr, is handed args-\u003ermtvaluelen.  That field is filled from the\non-disk __be32 xfs_attr_leaf_name_remote.valuelen in\nxfs_attr3_leaf_getvalue(), so a crafted length such as 0x80000000 is\nstored into the signed rmtvaluelen as a negative number.\n\nThe \"buffer too small\" guard in xfs_attr_copy_value() is a signed\ncomparison:\n\n\tif (args-\u003evaluelen \u003c valuelen)\n\t\treturn -ERANGE;\n\nA negative valuelen therefore compares as smaller than the caller\u0027s\nbuffer size, skips the -ERANGE path, and is then used as a copy length,\nleading to an out-of-bounds copy of a full remote block into a small\ngetxattr(2) buffer on a mounted crafted image.\n\nReject a value length that is negative or larger than the maximum xattr\nsize before it is used, so a bogus on-disk length can no longer slip\nthrough the value copier.",
  "id": "GHSA-pp64-v6p6-8mv7",
  "modified": "2026-11-19T15:31:23Z",
  "published": "2026-11-19T15:31:23Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99400"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/0643549ffecaeb716c0b75590a9b76dfa5eb35b3"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/91d0cf6244280e67bdc2787a60a10f635ac064c0"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c2cd6b3b480ef2ae9752ed924a2199c8c90569a1"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/c5c34a0a5a80ecd8fea9fff960907b2924d18cd9"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



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.