CVE-2026-64401

In the Linux kernel, the following vulnerability has been resolved: smb: client: resolve SWN tcon from live registrations cifs_swn_notify() looks up a witness registration by id under cifs_swnreg_idr_mutex, drops the mutex, and then uses the registration's cached tcon pointer. That pointer is not a lifetime reference, and it is not a stable representative once cifs_get_swn_reg() lets multiple tcons for the same net/share name share one registration id. A same-share second mount can keep the cifs_swn_reg alive after the first tcon unregisters and is freed. The registration then still points at the freed first tcon, so taking tc_lock or incrementing tc_count through swnreg->tcon only moves the use-after-free earlier. Taking tc_lock while holding cifs_swnreg_idr_mutex also violates the documented CIFS lock order. Fix this by making the registration store only the stable witness identity: id, net name, share name, and notify flags. When a notify arrives, copy that identity under cifs_swnreg_idr_mutex, drop the mutex, then find and pin a live witness tcon that currently matches the net/share pair under the normal cifs_tcp_ses_lock -> tc_lock order. The notification path uses that pinned tcon directly and drops the reference when done. Registration and unregister messages now use the live tcon passed by the caller instead of a cached tcon in the registration. The final unregister send is folded into cifs_swn_unregister() while the registration is still protected by cifs_swnreg_idr_mutex. This removes the previous find/drop/reacquire raw-pointer window. The release path only removes the idr entry and frees the stable identity strings. This preserves the intended one-registration/many-tcon behavior: a registration id represents a net/share pair, and notify handling acts on a live representative selected at use time. It also preserves CLIENT_MOVE ordering for the representative tcon because the old-IP unregister is sent before cifs_swn_register() sends the new-IP register.

• https://git.kernel.org/stable/c/0700f946659d0ab2352ec8a9b1c6fc74b13a27d7
• https://git.kernel.org/stable/c/51d18db392e5386a7bb9e816d611f14e600cca3c
• https://git.kernel.org/stable/c/91b8a58c6ac15c7db6518f696389933282f88da7
• https://git.kernel.org/stable/c/945b4a4a54497db1dcb2f20ef801a84e884dac21
• https://git.kernel.org/stable/c/aa3c0cab4b28c5007ec570c63e1d6ad6943ed0fd
• https://git.kernel.org/stable/c/ec457f9afe5ae9538bdcd58fd4cb442b9787e183

Published

Jul 25, 2026

Last Modified

Aug 11, 2026

Status

Awaiting Analysis

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-64396In the Linux kernel, the following vulnerability has been re…8.8
• CVE-2026-64397In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-64398In the Linux kernel, the following vulnerability has been re…8.1
• CVE-2026-64399In the Linux kernel, the following vulnerability has been re…9.8
• CVE-2026-6440The GoodMeet – Google Meet Integration for Webinar, Meeting …4.3
• CVE-2026-64400In the Linux kernel, the following vulnerability has been re…8.6
• CVE-2026-64402In the Linux kernel, the following vulnerability has been re…7.8
• CVE-2026-64403In the Linux kernel, the following vulnerability has been re…7.1
• CVE-2026-64404In the Linux kernel, the following vulnerability has been re…
• CVE-2026-64405In the Linux kernel, the following vulnerability has been re…
• CVE-2026-64406In the Linux kernel, the following vulnerability has been re…8
• CVE-2026-64407In the Linux kernel, the following vulnerability has been re…