GHSA-HFC2-HHFQ-7MQP

Vulnerability from github – Published: 2026-11-20 06:32 – Updated: 2026-11-20 06:32
VLAI
Details

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

ovl: fix whiteout creation in casefolded directories

unlink and rmdir fail with EINVAL on an overlay with casefolded (case-insensitive) layers, if the name exists in a lower layer. Casefolded layers need CONFIG_UNICODE. Root can mount such an overlay, and so can an unprivileged user in a user namespace, with tmpfs layers.

Overlayfs does not change a lower layer. To remove a name that exists there, it hides the name with a marker file, a whiteout. It creates the whiteout in the work directory, a scratch directory on the upper filesystem, and renames it over the name in the upper directory:

  • ovl_whiteout() creates the whiteout with mknod, or as a hard link to an earlier whiteout.
  • ovl_cleanup_and_whiteout() then prepares the rename with start_renaming_two_dentries(), which returns -EINVAL if the source or the target dentry is unhashed, that is, not in the dentry hash table.

With casefolded directories, both dentries can be unhashed:

  • The target. Lookup in a casefolded directory leaves a negative dentry unhashed, so the rename target is unhashed if the name does not exist in the upper directory.
  • The source, which is the new whiteout. tmpfs hashes a dentry when mknod or link makes it positive, but ext4 does not, so on ext4 the source is unhashed as well.

The cleanup after the failure also refuses an unhashed dentry, so on ext4 the whiteout is left behind in the work directory.

Reproduced with rm and rmdir on casefolded tmpfs and ext4 layers, also as uid 1000 in a user namespace.

Fix this by creating the whiteout with ovl_create_temp(), which repeats the lookup if the new dentry is unhashed. Prepare the rename with start_renaming_dentry(), which looks up the target name with the directories locked. The caller looked the name up without a lock, so return -ESTALE if the name now refers to a different inode.

[amir: pass the name used for lookup instead of taking a name snapshot]

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-99639"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-11-20T06:17:57Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\novl: fix whiteout creation in casefolded directories\n\nunlink and rmdir fail with EINVAL on an overlay with casefolded\n(case-insensitive) layers, if the name exists in a lower layer.\nCasefolded layers need CONFIG_UNICODE. Root can mount such an overlay,\nand so can an unprivileged user in a user namespace, with tmpfs layers.\n\nOverlayfs does not change a lower layer. To remove a name that exists\nthere, it hides the name with a marker file, a whiteout. It creates the\nwhiteout in the work directory, a scratch directory on the upper\nfilesystem, and renames it over the name in the upper directory:\n\n- ovl_whiteout() creates the whiteout with mknod, or as a hard link to\n  an earlier whiteout.\n- ovl_cleanup_and_whiteout() then prepares the rename with\n  start_renaming_two_dentries(), which returns -EINVAL if the source or\n  the target dentry is unhashed, that is, not in the dentry hash table.\n\nWith casefolded directories, both dentries can be unhashed:\n\n- The target. Lookup in a casefolded directory leaves a negative dentry\n  unhashed, so the rename target is unhashed if the name does not exist\n  in the upper directory.\n- The source, which is the new whiteout. tmpfs hashes a dentry when\n  mknod or link makes it positive, but ext4 does not, so on ext4 the\n  source is unhashed as well.\n\nThe cleanup after the failure also refuses an unhashed dentry, so on\next4 the whiteout is left behind in the work directory.\n\nReproduced with rm and rmdir on casefolded tmpfs and ext4 layers, also\nas uid 1000 in a user namespace.\n\nFix this by creating the whiteout with ovl_create_temp(), which repeats\nthe lookup if the new dentry is unhashed. Prepare the rename with\nstart_renaming_dentry(), which looks up the target name with the\ndirectories locked. The caller looked the name up without a lock, so\nreturn -ESTALE if the name now refers to a different inode.\n\n[amir: pass the name used for lookup instead of taking a name snapshot]",
  "id": "GHSA-hfc2-hhfq-7mqp",
  "modified": "2026-11-20T06:32:05Z",
  "published": "2026-11-20T06:32:05Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99639"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/48bd1823237fb076db6e109e35c59b1bc08f550a"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/e803c82dcdd15e87b48fca1ea8d2cfe6a7ed83d4"
    }
  ],
  "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.