smb: client: use finish_no_open() for non-regular inodes
Summary
| CVE | CVE-2026-98451 |
|---|---|
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-18 16:16:55 UTC |
| Updated | 2026-10-24 14:16:42 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 8.8 HIGH from 416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS: 0.001680000 probability, percentile 0.057460000 (date 2026-10-21)
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | Secondary | 8.8 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| 3.1 | CNA | DECLARED | 8.8 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
NoneUser Interaction
RequiredScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Linux | Linux | affected d2c127197dfc0b2bae62a52e1e0d3e3ff493919e 045532f920d86dd76600b635f9756e5fd671ddfc git | Not specified |
| CNA | Linux | Linux | affected d2c127197dfc0b2bae62a52e1e0d3e3ff493919e ed03d547598c92a036f20e89156540995cac889a git | Not specified |
| CNA | Linux | Linux | affected d2c127197dfc0b2bae62a52e1e0d3e3ff493919e 70a7918fda54a06d836acc91eb9a3c7e860fe0a0 git | Not specified |
| CNA | Linux | Linux | affected d2c127197dfc0b2bae62a52e1e0d3e3ff493919e 3c07deb26273155c180aedfd9041ab58015d2521 git | Not specified |
| CNA | Linux | Linux | affected d2c127197dfc0b2bae62a52e1e0d3e3ff493919e e66cf1625ec4a3fe68346119f371def713fd0a4d git | Not specified |
| CNA | Linux | Linux | affected 3.6 | Not specified |
| CNA | Linux | Linux | unaffected 3.6 semver | Not specified |
| CNA | Linux | Linux | unaffected 6.6.160 6.6.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.12.113 6.12.* semver | Not specified |
| CNA | Linux | Linux | unaffected 6.18.56 6.18.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.2.9 7.2.* semver | Not specified |
| CNA | Linux | Linux | unaffected 7.3 * original_commit_for_fix | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| git.kernel.org/stable/c/70a7918fda54a06d836acc91eb9a3c7e860fe0a0 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/e66cf1625ec4a3fe68346119f371def713fd0a4d | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/ed03d547598c92a036f20e89156540995cac889a | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/045532f920d86dd76600b635f9756e5fd671ddfc | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| git.kernel.org/stable/c/3c07deb26273155c180aedfd9041ab58015d2521 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 | git.kernel.org | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.