CVE-2026-97556

smb: client: avoid leaking refcount when cifs_sb_tlink() fails

N/A
Published: September 25, 2026 at 10:21 AM UTC
Updated: October 19, 2026 at 10:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: avoid leaking refcount when cifs_sb_tlink() fails cifs_oplock_break() takes over the reference that cifs_queue_oplock_break() acquired when it queued the work, and drops it with _cifsFileInfo_put() once the break has been processed. Only in setups with "-o multiuser", cifs_sb_tlink() may fail, at which point cifs_oplock_break() returns without putting the file reference, mirroring the reference leak we already fixed in the companion patch to cifs_queue_oplock_break(). This would trigger a crash due to busy inodes on the next unmount: BUG: Dentry ... still in use (1) [unmount of cifs cifs] VFS: Busy inodes after unmount of cifs (cifs) Drop the reference on that path as well. Doing so before the out label mirrors the normal path, which also puts the reference before cifs_done_oplock_break(). Found by Sashiko code review. The failure path was not exercised at runtime.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.15.1285ee28bcfbaacf289eb25c662a2862542ea6ce6a76.1.476.4.126.56b67a6d2e50634fe127e656147c81915955e9f5eb99f490ea87ebcca3a429fd8837067feb56a4c7ce8f5f849ffce24490eb9449e98312b66c0dba76f
Vendor states this is fixed in 1d1b0f1d812a4011a57bc6c70492c34a2e46c6dd (fixed)
Vendor states this is fixed in 23b26f4408ac3f35a482d2e5cf6fc865d4201b71 (fixed)
Vendor states this is fixed in 55c5f095d4df14271b238f826e1392fda7b6e60e (fixed)
Vendor states this is fixed in 9ec991e148368e3207e98134c509a625097f7693 (fixed)
Vendor states this is fixed in dd03fd658ea59821505e0e643b6b7cbdf51c4e1d (fixed)
Vendor states this is fixed in e9c5bcc88b8337157e480c85a6d2f326bc265012 (fixed)
Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.1.189 (unaffected)
Vendor states this is fixed in 6.12.111 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 6.5 (unaffected)
Vendor states this is fixed in 6.6.158 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc3 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card