CVE-2026-64386: smb: client: fix query_info() replay double-free

From: Greg Kroah-Hartman <[email protected]>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

smb: client: fix query_info() replay double-free

A response-bearing attempt can return a replayable error and free its
response buffer. If SMB2_query_info_init() fails before the next send,
cleanup retains the previous buffer type and frees that response again.

Reset response bookkeeping before each attempt to prevent the stale free.

The Linux kernel CVE team has assigned CVE-2026-64386 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.6.32 with commit 433042a91f9373241307725b52de573933ffedbf and fixed in 6.6.145 with commit 100fb7c455fa86d248b8bd7bb9de757c192870b4
	Issue introduced in 6.8 with commit 4f1fffa2376922f3d1d506e49c0fd445b023a28e and fixed in 6.12.96 with commit 3c81dda84799f76b42aec598564316e2964440db
	Issue introduced in 6.8 with commit 4f1fffa2376922f3d1d506e49c0fd445b023a28e and fixed in 6.18.39 with commit f1add4acb656f5a82806a1ab0e63fed3d8b1bfca
	Issue introduced in 6.8 with commit 4f1fffa2376922f3d1d506e49c0fd445b023a28e and fixed in 7.1.4 with commit 89234773e8348918111aa15f6922b58cf3843364
	Issue introduced in 6.8 with commit 4f1fffa2376922f3d1d506e49c0fd445b023a28e and fixed in 7.2-rc1 with commit 2a88561d66eb855813cf004a0abe648bbb17de5e

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2026-64386
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	fs/smb/client/smb2pdu.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/100fb7c455fa86d248b8bd7bb9de757c192870b4
	https://git.kernel.org/stable/c/3c81dda84799f76b42aec598564316e2964440db
	https://git.kernel.org/stable/c/f1add4acb656f5a82806a1ab0e63fed3d8b1bfca
	https://git.kernel.org/stable/c/89234773e8348918111aa15f6922b58cf3843364
	https://git.kernel.org/stable/c/2a88561d66eb855813cf004a0abe648bbb17de5e