Skip to main content
VulnerabilityPublished

CVE-2026-99382: Linux kernel · smb: client: reject FIND data areas that run past the received response

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99382

Not known to be exploited · fixed in dbc8b87b91b1838beb3e7135a592bbbbd7741404 : update Linux kernel when convenient.

Data as of 19 Nov 2026, 16:20 UTC

Severity
Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in dbc8b87b91b1838beb3e7135a592bbbbd7741404, 9763e65a0a4588217cee2c05a00f1023820519b9, 29bd6773187cb5c1bbbdf90d677c6add7d58af26 +1

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Linux kernel to dbc8b87b91b1838beb3e7135a592bbbbd7741404, 9763e65a0a4588217cee2c05a00f1023820519b9, 29bd6773187cb5c1bbbdf90d677c6add7d58af26 or 4dfc78e53f419834d99e626fc27083799e2ea4c1.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < dbc8b87b91b1838beb3e7135a592bbbbd7741404
Fixed in
  • dbc8b87b91b1838beb3e7135a592bbbbd7741404
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 9763e65a0a4588217cee2c05a00f1023820519b9
Fixed in
  • 9763e65a0a4588217cee2c05a00f1023820519b9
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 29bd6773187cb5c1bbbdf90d677c6add7d58af26
Fixed in
  • 29bd6773187cb5c1bbbdf90d677c6add7d58af26
LinuxLinuxAffected
  • ≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, < 4dfc78e53f419834d99e626fc27083799e2ea4c1
Fixed in
  • 4dfc78e53f419834d99e626fc27083799e2ea4c1
LinuxLinuxAffected
  • =2.6.12
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: reject FIND data areas that run past the received response CIFSFindFirst() and CIFSFindNext() take the directory entries of a TRANS2_FIND_FIRST2 or TRANS2_FIND_NEXT2 response from DataOffset for DataCount bytes. validate_t2() bounds DataOffset at 1024 and ParameterCount + DataCount by the byte count, and nothing compares DataOffset + DataCount with the number of bytes SendReceive() copied into the buffer. smb_init() places the request and the response in the same cifs_request allocation and cifs_buf_get() clears only the start of it, so a short response whose data area extends past its end has srch_entries_start point at bytes of the request that was just sent, or at whatever the allocation held before, and those bytes are parsed as directory entries. cifs_readdir() and find_cifs_entry() walk the entries with nxt_dir_entry(), which checks every entry but the first of a response against the end of the SMB; cifs_query_path_info() and cifs_backup_query_path_info() read the first entry with no check at all. Those reads stay inside the allocation, but what they return is not part of the response. The last entry, which LastNameOffset locates relative to the data area, is bounded against the received response by an earlier patch of this series, as is every entry that cifs_fill_dirent() parses; the walk itself and the two query functions are not. SMB1 is not negotiated by default; reaching this code requires an explicit vers=1.0 mount. Reject a response whose data area extends past the received length, with the -EINVAL that validate_t2() returns for the other malformed transaction responses. cifs_query_path_info() and cifs_backup_query_path_info() still read a whole entry from a data area that may be smaller than one; that is not changed here. A conforming server is not affected. The data block of a transaction response is part of the SMB, so DataOffset + DataCount cannot exceed the smbCalcSize() bytes that SendReceive() copies; coalesce_t2() appends each secondary response to the data area and adds its length to both DataCount and the byte count, which keeps that relation.

References

Community reviews

Loading reviews…