CVE-2026-99295 · Package
NO FIX YET
When the Linux kernel's CIFS/SMB client hits a socket receive error during a read, it can keep using a request buffer that was already freed. A malicious or faulty SMB server could turn this into memory corruption in the kernel.
first public Nov 16, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Systems that mount SMB/CIFS shares through the Linux kernel client and read data from them are the ones exposed. Machines that never mount CIFS shares, or that run without the cifs module, are not affected. The sources do not give the exact kernel ranges.
Not affected if cifs-module-not-loaded, no-cifs-mounts
Who cares cifs, file-servers, linux-kernel, smb
uname -r and compare it to the fixed kernel versions from the kernel stable tree (unknown: the sources do not list them)lsmod | grep cifsUnknown from the sources.
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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.