CVE-2026-99425
ovl: hold a reference on the parent in readdir
What happened?
In the Linux kernel, the following vulnerability has been resolved:
ovl: hold a reference on the parent in readdir
Listing a directory on an overlay uses a freed dentry and crashes the kernel when a lookup moves the directory at the same time.
Code that can sleep may only use d_parent without a reference while something stops a move of the dentry. ovl_iterate_real(), ovl_need_adjust_d_ino() and ovl_cache_update() use the d_parent of the listed directory and hold only the lock of that directory. When a lookup finds the directory under another parent after a change to a layer, d_splice_alias() moves it without that lock and drops its reference on the old parent.
With a delay in ovl_iterate_real(), getdents64 on an overlay directory raced a rename in the lower layer and a lookup that moved its dentry, and after an rmdir of the old parent KASAN reported a use-after-free in security_inode_getattr().
Fix this by using dget_parent() in the three functions.
[amir: fix comments in ovl_need_adjust_d_ino()]
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: b5efccbe0a12a9d5c65c1a60b4270837c7fdb900 to < 862804fc1d8e6d11652d01f84451a0c9396d10cd; affected: b5efccbe0a12a9d5c65c1a60b4270837c7fdb900 to < 0759376aa01168edeec9319f9cc8e5e9b9388c5c; affected: b5efccbe0a12a9d5c65c1a60b4270837c7fdb900 to < 73aae2a6b5b34b4ee5dbc7b008fc658c2a16fcea; affected: b5efccbe0a12a9d5c65c1a60b4270837c7fdb900 to < 16d319e12328acafeafd3eecdf09c46d7fb43452 | See vendor advisory |
| LinuxLinux | affected: 4.14; unaffected: 0 to < 4.14; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99425
- https://git.kernel.org/stable/c/862804fc1d8e6d11652d01f84451a0c9396d10cd
- https://git.kernel.org/stable/c/0759376aa01168edeec9319f9cc8e5e9b9388c5c
- https://git.kernel.org/stable/c/73aae2a6b5b34b4ee5dbc7b008fc658c2a16fcea
- https://git.kernel.org/stable/c/16d319e12328acafeafd3eecdf09c46d7fb43452