CVE-2026-99384

Source
https://cve.org/CVERecord?id=CVE-2026-99384
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99384.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99384
Downstream
Published
2026-11-19T14:23:24Z
Modified
2026-11-19T17:01:08Z
Summary
smb: client: fix OOB read of the resume name sent in TRANS2_FIND_NEXT2
Details

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

smb: client: fix OOB read of the resume name sent in TRANS2_FIND_NEXT2

cifs_fill_dirent() reads the fixed part of a directory entry and the name length it holds, or for SMB_FIND_FILE_UNIX scans the name for its terminating NUL, without knowing where the response ends. cifs_save_resume_key() calls it for the entry at the LastNameOffset the server chose, after every FindNext and after the FindFirst of a search rewind, and records the name it returns as the resume name of the search without bounding it; the next CIFSFindNext() copies up to PATH_MAX - 1 bytes from that name into its request and sends them to the server. cifs_filldir() bounds the name against the end of the response since commit f8cf09a53a0d ("smb: client: bound dirent name against end of SMB response in cifs_filldir"), but only after cifs_fill_dirent() has read the entry, and nxt_dir_entry() checks the entries it walks only against sizeof(FILE_DIRECTORY_INFO), for every level but SMB_FIND_FILE_INFO_STANDARD, and never sees the first entry of a response.

Bounding where last_entry starts, as the preceding patch does, does not bound the read. A last entry that starts within the final bytes of the response still has its fixed part read past the end of the received data, and the name length it declares, a __le32 for every level but SMB_FIND_FILE_INFO_STANDARD and SMB_FIND_FILE_UNIX, is recorded without being checked against anything. CIFSFindNext() rejects only a length of PATH_MAX or more, then copies the name, up to 4095 bytes, into its request and sends it, and as the report below shows that copy can run past the end of the cifs_request allocation that holds the response. For SMB_FIND_FILE_UNIX the name is in addition scanned for its terminating NUL over up to PATH_MAX + 1 UTF-16 units, or PATH_MAX bytes, before any check. The FindNext that carries the name is only sent by the SMB1 dialect, which is not negotiated by default; reaching it requires an explicit vers=1.0 mount.

With KASAN enabled, a response whose last entry declares a name longer than the bytes that follow it gives:

================================================================== BUG: KASAN: slab-out-of-bounds in CIFSFindNext+0x8ca/0x14c0 Read of size 4080 at addr ffff88807c823f98 by task ls/83

CPU: 0 UID: 0 PID: 83 Comm: ls Not tainted 7.3.0-rc4-00457-gf14572c203d5 #69 PREEMPT(lazy) Call Trace: kasan_report+0xdf/0x1a0 kasan_check_range+0x10f/0x1e0 __asan_memcpy+0x23/0x60 CIFSFindNext+0x8ca/0x14c0 cifs_readdir+0xf51/0x29c0 iterate_dir+0x1c0/0x570 __x64_sys_getdents64+0x133/0x270 do_syscall_64+0x109/0x5d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Allocated by task 83 on cpu 1 at 13.497119s: cifs_buf_get+0x36/0x90 smb_init+0x4f/0x110 CIFSFindNext+0xf7/0x14c0 cifs_readdir+0xf51/0x29c0

The buggy address belongs to the object at ffff88807c820000 which belongs to the cache cifs_request of size 16588 The buggy address is located 16280 bytes inside of allocated 16588-byte region [ffff88807c820000, ffff88807c8240cc)

The read is the memcpy() that copies the recorded name into the next request, so those bytes go to the server.

Pass the end of the response to cifs_fill_dirent() and have it reject an entry whose fixed part does not fit or whose name extends past the end, before either is used, so that both callers are covered; cifs_save_resume_key() computes the end the same way cifs_readdir() does. The name bound compares the bytes left between the name and the end with the name length rather than adding the length to the name pointer, since the length is a 32-bit value taken from the entry and the sum could wrap on 32-bit systems. cifs_fill_dirent() is also used on the SMB2 readdir path; there smb2_parse_query_directory() has already checked every entry against the end of the response, so a vali ---truncated---

Database specific
{
    "cna_assigner":  "Linux",
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99384.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
0752f1522a9120f731232919f7ad904e9e22b8ce
Fixed
0cc7589ab18a891eb9aa8621f76e1eb09a6d0704
Fixed
556c3a72f58e0ce4356d57301712cbcd7b2e4c65
Fixed
7141cde58f9dc15cf0869529ba2cb09fb0f082e5
Fixed
f8171804a39ee89a11cd462f67862899de9c6b10
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
bc15485e6a3cd20829cfa58bc9111e0bfc9cf303
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
282333bd7f759cdd9362e793b85db08780516416
Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
92fa67e9260a65f69d868c4fcc92c9cee428c6f9

Affected versions

v2.*
v2.6.25.19
v2.6.25.20
v2.6.26.7
v2.6.26.8
v2.6.27.10
v2.6.27.11
v2.6.27.12
v2.6.27.13
v2.6.27.14
v2.6.27.15
v2.6.27.16
v2.6.27.17
v2.6.27.18
v2.6.27.19
v2.6.27.2
v2.6.27.20
v2.6.27.21
v2.6.27.22
v2.6.27.23
v2.6.27.24
v2.6.27.25
v2.6.27.26
v2.6.27.27
v2.6.27.28
v2.6.27.29
v2.6.27.3
v2.6.27.30
v2.6.27.31
v2.6.27.32
v2.6.27.33
v2.6.27.34
v2.6.27.35
v2.6.27.36
v2.6.27.37
v2.6.27.38
v2.6.27.39
v2.6.27.4
v2.6.27.40
v2.6.27.41
v2.6.27.42
v2.6.27.43
v2.6.27.44
v2.6.27.45
v2.6.27.46
v2.6.27.47
v2.6.27.48
v2.6.27.49
v2.6.27.5
v2.6.27.50
v2.6.27.51
v2.6.27.52
v2.6.27.53
v2.6.27.54
v2.6.27.55
v2.6.27.56
v2.6.27.57
v2.6.27.58
v2.6.27.59
v2.6.27.6
v2.6.27.60
v2.6.27.61
v2.6.27.62
v2.6.27.7
v2.6.27.8
v2.6.27.9

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99384.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
2.6.25.19
Fixed
2.6.26
Type
ECOSYSTEM
Events
Introduced
2.6.26.7
Fixed
2.6.27
Type
ECOSYSTEM
Events
Introduced
2.6.27.2
Fixed
2.6.28
Type
ECOSYSTEM
Events
Introduced
2.6.28
Fixed
6.12.118
Type
ECOSYSTEM
Events
Introduced
6.13.0
Fixed
6.18.64
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.3.2

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99384.json"