CVE-2026-99295
smb: client: stop processing a read response after a receive error
What happened?
In the Linux kernel, the following vulnerability has been resolved:
smb: client: stop processing a read response after a receive error
cifs_read_iter_from_socket() may call cifs_reconnect() before returning an error. The reconnect path aborts pending mids and invokes their callbacks. The callback can then release the cifs_io_subrequest containing rdata.
cifs_readv_receive() nevertheless continues after a negative return and may dereference rdata in cifs_readv_discard(). KASAN reports the resulting UAF:
BUG: KASAN: slab-use-after-free in cifs_readv_receive Read of size 4 by task cifsd cifs_readv_receive (fs/smb/client/transport.c:1284) cifs_demultiplex_thread (fs/smb/client/connect.c:1355) kthread (kernel/kthread.c:436) ret_from_fork (arch/x86/kernel/process.c:158)
Freed by task 148: netfs_put_subrequest (fs/netfs/objects.c:267) netfs_read_collection (fs/netfs/read_collect.c:460) netfs_wait_for_in_progress (fs/netfs/misc.c:462)
Return the socket error immediately, as this path did before the iterator conversion. This also avoids adding a negative length to total_read.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: d08089f649a0cfb2099c8551ac47eef0cc23fdf2 to < af78baeacd731a98531eaa3103bfe03f147cffb7; affected: d08089f649a0cfb2099c8551ac47eef0cc23fdf2 to < ecc327edd96a65ac177379664cc0972d8a23dfa4; affected: d08089f649a0cfb2099c8551ac47eef0cc23fdf2 to < 558cb79cb242ce7ca8b32c4b39412d125879e8f2; affected: d08089f649a0cfb2099c8551ac47eef0cc23fdf2 to < 51efca72345acdbedc4af76782d464bd15ba50ff | See vendor advisory |
| LinuxLinux | affected: 6.3; unaffected: 0 to < 6.3; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99295
- https://git.kernel.org/stable/c/af78baeacd731a98531eaa3103bfe03f147cffb7
- https://git.kernel.org/stable/c/ecc327edd96a65ac177379664cc0972d8a23dfa4
- https://git.kernel.org/stable/c/558cb79cb242ce7ca8b32c4b39412d125879e8f2
- https://git.kernel.org/stable/c/51efca72345acdbedc4af76782d464bd15ba50ff