Linux kernel race in overlayfs triggers kernel warning
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The Linux kernel's overlayfs can log a kernel warning and make a stat() call fail with ECHILD when another task is creating the same file at that moment. Write access to a directory on an overlay with a FUSE upper layer is enough for a user to trigger it.
Written by a model
Original description
In the Linux kernel, the following vulnerability has been resolved:
ovl: set the revalidate flags after d_instantiate()
stat() of a file on an overlayfs mount triggers a kernel warning and fails with ECHILD if another task is creating that file at the same time. This happens on an overlay with a FUSE upper layer, which is the layer where overlayfs creates new files. Write access to a directory on such an overlay is all a user needs to run the two tasks.
The revalidate flags are DCACHE_OP_REVALIDATE and DCACHE_OP_WEAK_REVALIDATE. They tell path walk to call ->d_revalidate() or ->d_weak_revalidate() on a dentry, so that the filesystem can check that the cached dentry is still valid. An overlay dentry only has one of these flags if a dentry in one of its layers has it. FUSE dentries have the first one.
When a flag is set on an overlay dentry, path walk calls ovl_dentry_revalidate_common(). That function only expects a dentry without an inode in RCU walk, while the dentry is being destroyed. For such a dentry outside of RCU walk, it hits a WARN_ON() and returns -ECHILD. So a negative overlay dentry must never have the flags set.
ovl_instantiate() breaks this rule. When a task creates a file, the overlay dentry for the new name is hashed but still negative. ovl_instantiate() then works in this order:
- It copies the flags from the new upper dentry to the overlay dentry.
- It calls ovl_get_inode(), which can sleep in a getxattr request to the FUSE server.
- Only then does it call d_instantiate().
A second task that looks up the name between the first step and the last finds a negative dentry with the flags set and revalidates it.
Reproduced with a FUSE server that delays its getxattr reply: stat() of a name that was being created hit the WARN_ON() and failed with ECHILD.
Fix this by setting the flags after d_instantiate().
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-99415 (ovl: set the revalidate flags after d_instantiate()), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-99415 (entry last updated 2026-11-19):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 5.7
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99415 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99415 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/e876482d955476d0c066afda8273bfd38e0f65be
- https://git.kernel.org/stable/c/7ecbeb1a84f2d099012ccd95a8a7588e1306cc46
- https://git.kernel.org/stable/c/3d92153206cebe95dc873a4b2b3d506ddf2271e7
- https://git.kernel.org/stable/c/75e89c0055c1d7f7eeb462995f11253ca5864f79
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-99415
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99415"}.Affected versions
- Linux LinuxVersion range not reported
- Linux Linux5.7
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch5/5No patch listed yet
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 47 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 6
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99415 |
| Record | NVD · CVE-2026-99415 |
| Other links 4 | |
| Link | git.kernel.org · stable/c/e876482d955476d0c066afda8273bfd38e0f65be |
| Link | git.kernel.org · stable/c/7ecbeb1a84f2d099012ccd95a8a7588e1306cc46 |
| Link | git.kernel.org · stable/c/3d92153206cebe95dc873a4b2b3d506ddf2271e7 |
| Link | git.kernel.org · stable/c/75e89c0055c1d7f7eeb462995f11253ca5864f79 |
Questions about CVE-2026-99415
Is CVE-2026-99415 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-99415?
Linux: version 5.7.
Source: cve.now feed data
Related
- CVE-2026-99804io_uring/io-wq: save worker type before dropping its reference
- CVE-2026-99803io_uring/net: mask socket type with SOCK_TYPE_MASK in io_socket_bpf_populate()
- CVE-2026-99802io_uring/register: enforce per-task restrictions in io_uring_register_blind()
- CVE-2026-99801io_uring/bpf-ops: clear bpf_ctx while submitting SQEs
- CVE-2026-99800io_uring: free the task context after a grace period
- CVE-2026-99799io_uring/sqpoll: don't wait for the thread to exit
No corrections so far. Something wrong on this page? Report an error.