What’s Vulnerable › Vulnerabilities
CVE-2026-98451: smb: client: use finish_no_open() for non-regular inodes
- Severity: high (CVSS 8.8 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.4% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-10-18 · updated 2026-10-30
Description
In the Linux kernel, the following vulnerability has been resolved: smb: client: use finish_no_open() for non-regular inodes An O_CREAT open can find an existing symlink or another non-regular inode. cifs_atomic_open() calls finish_open() on it and attaches a cifsFileInfo. Symlink inodes have no CIFS release operation, so the dentry reference held by cifsFileInfo is leaked. FMODE_OPENED also prevents the VFS from following the symlink. Track whether cifs_do_create() returned an open server handle. For non-regular inodes, close the handle if present, remove the pending open, and call finish_no_open() so the VFS can continue the lookup. Do not set FMODE_CREATED unless a regular file was opened. For O_NOFOLLOW with __O_REGULAR, return -ELOOP before the VFS's -EFTYPE check. Defer closing a legacy POSIX handle on a non-regular inode until after inode lookup. This avoids closing it again if lookup fails.
Affected products
- Linux: 3.6 — fixed in 7.3
How to fix
Upgrade to a fixed version: Linux 7.3. Check the vendor advisory for mitigations.
References
- https://git.kernel.org/stable/c/045532f920d86dd76600b635f9756e5fd671ddfc
- https://git.kernel.org/stable/c/26f4bca335e719e291995e28dc434de0145a6a54
- https://git.kernel.org/stable/c/3c07deb26273155c180aedfd9041ab58015d2521
- https://git.kernel.org/stable/c/51c7b0593f6eaba05349fd2a01a9cb4df7d7412f
- https://git.kernel.org/stable/c/70a7918fda54a06d836acc91eb9a3c7e860fe0a0
- https://git.kernel.org/stable/c/bc585d5a381ab49cb611c35dda93a997214ca874
- https://git.kernel.org/stable/c/e66cf1625ec4a3fe68346119f371def713fd0a4d
- https://git.kernel.org/stable/c/ed03d547598c92a036f20e89156540995cac889a
Get alerted when CVE-2026-98451 or the next vulnerability affects your stack