CVE-2025-21654 Details
Description
In the Linux kernel, the following vulnerability has been resolved: ovl: support encoding fid from inode with no alias Dmitry Safonov reported that a WARN_ON() assertion can be trigered by userspace when calling inotify_show_fdinfo() for an overlayfs watched inode, whose dentry aliases were discarded with drop_caches. The WARN_ON() assertion in inotify_show_fdinfo() was removed, because it is possible for encoding file handle to fail for other reason, but the impact of failing to encode an overlayfs file handle goes beyond this assertion. As shown in the LTP test case mentioned in the link below, failure to encode an overlayfs file handle from a non-aliased inode also leads to failure to report an fid with FAN_DELETE_SELF fanotify events. As Dmitry notes in his analyzis of the problem, ovl_encode_fh() fails if it cannot find an alias for the inode, but this failure can be fixed. ovl_encode_fh() seldom uses the alias and in the case of non-decodable file handles, as is often the case with fanotify fid info, ovl_encode_fh() never needs to use the alias to encode a file handle. Defer finding an alias until it is actually needed so ovl_encode_fh() will not fail in the common case of FAN_DELETE_SELF fanotify events.
A vulnerability in the Linux kernel's OverlayFS implementation can be triggered by userspace interactions with inotify. When an OverlayFS inode's dentry aliases are discarded, the inotify_show_fdinfo() function can encounter a WARN_ON() assertion failure. This issue arises because the function fails to encode the file handle for the OverlayFS inode, which is critical for proper event reporting. The problem stems from the ovl_encode_fh() function's reliance on finding an alias for the inode, a step that can be deferred to avoid failures in common scenarios, such as with FAN_DELETE_SELF events.
No specific remediation is provided, but the issue has been addressed in the Linux kernel.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/3c7c90274ae339e1ad443c9be1c67a20b80b9c76 | kernel.org | Patch |
| https://git.kernel.org/stable/c/c45beebfde34aa71afbc48b2c54cdda623515037 | kernel.org | Patch |
| https://git.kernel.org/stable/c/f0c0ac84de17c37e6e84da65fb920f91dada55ad | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-617 | Reachable Assertion | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.6, < 6.6.74 >= 6.7, < 6.12.10 6.13 rc1 6.13 rc2 6.13 rc3 6.13 rc4 6.13 rc5 6.13 rc6 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Sep 26, 2025 | Initial Analysis | [email protected] |
| Jan 24, 2025 | CVE Modified | kernel.org |
| Jan 23, 2025 | CVE Modified | kernel.org |
| Jan 21, 2025 | CVE Modified | kernel.org |
| Jan 19, 2025 | New CVE Received | kernel.org |