GHSA-PHP5-H7FX-PMGJ
Vulnerability from github – Published: 2026-11-19 15:31 – Updated: 2026-11-19 15:31In the Linux kernel, the following vulnerability has been resolved:
ovl: set OVL_WHITEOUTS before publishing the upper dir
Listing a directory while it is copied up causes a use-after-free of the readdir cache.
A merge directory must never be iterated as a real upper directory: that mode frees the cache in OVL_I(inode)->cache without looking at its refcount, while files opened in merged mode still use it. ovl_copy_up_workdir() publishes the upper dentry before it sets OVL_WHITEOUTS, and ovl_dir_open() samples both without a lock, so an open between the two stores finds the upper directory and takes it for a real one.
With a delay between the two stores, an unprivileged process that listed a directory during its copy-up saw only "." and "..", and its next getdents freed the readdir cache of another descriptor.
Fix this by setting OVL_WHITEOUTS before ovl_inode_update(), so that ovl_dir_reset() agrees with ovl_dir_open(), and by testing OVL_TYPE_MERGE() of the path type in ovl_dir_open(), so that an open that observes the upper dentry never iterates a merge dir as a real dir, regardless of the order in which it observes the flag.
[amir: test OVL_TYPE_MERGE() instead of smp_rmb() in ovl_dir_open()]
{
"affected": [],
"aliases": [
"CVE-2026-99424"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-19T15:17:55Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\novl: set OVL_WHITEOUTS before publishing the upper dir\n\nListing a directory while it is copied up causes a use-after-free of\nthe readdir cache.\n\nA merge directory must never be iterated as a real upper directory:\nthat mode frees the cache in OVL_I(inode)-\u003ecache without looking at\nits refcount, while files opened in merged mode still use it.\novl_copy_up_workdir() publishes the upper dentry before it sets\nOVL_WHITEOUTS, and ovl_dir_open() samples both without a lock, so an\nopen between the two stores finds the upper directory and takes it\nfor a real one.\n\nWith a delay between the two stores, an unprivileged process that\nlisted a directory during its copy-up saw only \".\" and \"..\", and its\nnext getdents freed the readdir cache of another descriptor.\n\nFix this by setting OVL_WHITEOUTS before ovl_inode_update(), so that\novl_dir_reset() agrees with ovl_dir_open(), and by testing\nOVL_TYPE_MERGE() of the path type in ovl_dir_open(), so that an open\nthat observes the upper dentry never iterates a merge dir as a real\ndir, regardless of the order in which it observes the flag.\n\n[amir: test OVL_TYPE_MERGE() instead of smp_rmb() in ovl_dir_open()]",
"id": "GHSA-php5-h7fx-pmgj",
"modified": "2026-11-19T15:31:24Z",
"published": "2026-11-19T15:31:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99424"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/43ad4a3090e1c2a0c34e9802882b42c5c078d556"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7805739ce4577f2c53f5a30be2d48e83e91c63bc"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/cbec8610ec5aaf35df50094ff639febc23f20773"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/ea5327a9228bfd1609e54f1fca50786e8f963da5"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
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
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.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
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.