Linux kernel data exposure via race in overlayfs redirects
- Exploited
- No known exploitation
- Fix
- Fixed in 4.15, 4.20, 5.5, 5.11
- Who is exposed
- Not reported
Summary
In the Linux kernel, a hard link to a file raced with a rename of one of its ancestor directories can store a redirect that points to the wrong lower file. An unprivileged user can use this to make the file show the data of a root-only file after a remount.
Written by a model
Original description
In the Linux kernel, the following vulnerability has been resolved:
ovl: fix a torn path in ovl_get_redirect()
A hard link of a metacopy file that races with a rename of an ancestor stores a redirect to the wrong lower file.
Each component of an absolute redirect must be the name that a dentry has in the parent that the walk continues with. ovl_get_redirect() copies the name under d_lock and calls dget_parent() after the unlock, and the callers for a hard link hold no lock that stops a rename across directories. A rename between the two steps combines the old name with the new parent.
With delays in ovl_get_redirect(), an unprivileged user hard-linked a metacopy file while renaming its ancestor to another directory, the stored redirect named another lower path, and after a remount the file showed the data of a root-only file.
Fix this by taking the parent first and checking it again under d_lock.
What to do
Upgrade to a fixed version: 4.15, 4.20, 5.5, 5.11.
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-99417 (ovl: fix a torn path in ovl_get_redirect()), 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-99417 (entry last updated 2026-11-19):
Affected:
- Linux Linux: from 4.14.221, fixed in 4.15; from 4.19.175, fixed in 4.20; from 5.4.97, fixed in 5.5; from 5.10.15, fixed in 5.11
- Linux Linux: versions 5.11
Fixed versions: 4.15, 4.20, 5.5, 5.11.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99417 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99417 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/a8ad9bba205f7c6f3b86fcf0bd2d98adcd750f2e
- https://git.kernel.org/stable/c/b9f57bb52124aec87bbe344d70a30806fe22b992
- https://git.kernel.org/stable/c/0aa08f8f07872b9f67ab20d4c51e0cf6fc924714
- https://git.kernel.org/stable/c/2001cd7ca5560198131e46c6ca3c3472b06145c2
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-99417
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-99417"}.Affected versions
- Linux LinuxFrom 4.14.221 · fixed in 4.15; From 4.19.175 · fixed in 4.20; From 5.4.97 · fixed in 5.5; From 5.10.15 · fixed in 5.11
- Linux Linux5.11
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 patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 42 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-99417 |
| Record | NVD · CVE-2026-99417 |
| Other links 4 | |
| Link | git.kernel.org · stable/c/a8ad9bba205f7c6f3b86fcf0bd2d98adcd750f2e |
| Link | git.kernel.org · stable/c/b9f57bb52124aec87bbe344d70a30806fe22b992 |
| Link | git.kernel.org · stable/c/0aa08f8f07872b9f67ab20d4c51e0cf6fc924714 |
| Link | git.kernel.org · stable/c/2001cd7ca5560198131e46c6ca3c3472b06145c2 |
Questions about CVE-2026-99417
Is CVE-2026-99417 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-99417?
Linux: from 4.14.221 before 4.15; from 4.19.175 before 4.20; from 5.4.97 before 5.5; from 5.10.15 before 5.11. Linux: version 5.11.
Source: cve.now feed data
How do I fix CVE-2026-99417?
Upgrade to a fixed version: 4.15, 4.20, 5.5, 5.11.
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.