Strix
64.7K

CVE-2026-97556

Unknown

Last modified

CVE-2026-97556 is a vulnerability of currently unknown severity. 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.

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 Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= e8f5f849ffce24490eb9449e98312b66c0dba76f, < 9ec991e148368e3207e98134c509a625097f7693; >= e8f5f849ffce24490eb9449e98312b66c0dba76f, < dd03fd658ea59821505e0e643b6b7cbdf51c4e1d; >= e8f5f849ffce24490eb9449e98312b66c0dba76f, < 1d1b0f1d812a4011a57bc6c70492c34a2e46c6dd; >= e8f5f849ffce24490eb9449e98312b66c0dba76f, < 23b26f4408ac3f35a482d2e5cf6fc865d4201b71; b99f490ea87ebcca3a429fd8837067feb56a4c7c; 5ee28bcfbaacf289eb25c662a2862542ea6ce6a7; 6b67a6d2e50634fe127e656147c81915955e9f5e; >= 5.15.128, < 5.16; >= 6.1.47, < 6.2; >= 6.4.12, < 6.5
LinuxLinux6.5

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-97556?
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.
How severe is CVE-2026-97556?
Severity scoring for CVE-2026-97556 is pending analysis.
How do I fix CVE-2026-97556?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-97556?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST