---
id: "CVE-2026-99295"
page: "https://infrastack.ai/live/CVE-2026-99295"
kind: "vulnerability"
aliases: ["CVE-2026-99295"]
title: "Linux kernel SMB client: use-after-free after a receive error"
severity: "unknown"
cvss: null
epss: 0.00209
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["cifs", "file-servers", "linux-kernel", "package", "smb"]
not_affected_if: ["cifs-module-not-loaded", "no-cifs-mounts"]
published_at: "2026-11-16T10:17:02+00:00"
first_seen_at: "2026-11-16T10:39:26+00:00"
updated_at: "2026-11-16T18:53:18+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99295", "first_seen_at": "2026-11-16T10:39:26+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-99295", "first_seen_at": "2026-11-16T18:53:18+00:00"}]
exploit_sources: [{"type": "epss", "score": 0.00209, "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-99295"}]
---

# Linux kernel SMB client: use-after-free after a receive error

Link for people: https://infrastack.ai/live/CVE-2026-99295 (this .md is for agents)

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.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the running kernel version with `uname -r` and compare it to the fixed kernel versions from the kernel stable tree (unknown: the sources do not list them)
- Check whether the SMB client module is loaded with `lsmod | grep cifs`

## Timeline

- 2026-11-16T10:39:26+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-99295
- 2026-11-16T18:53:18+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-99295

## 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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
