Skip to main content
VulnerabilityPublished

CVE-2026-99380: Linux kernel · smb: client: validate NT transaction response layout and offsets

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99380

Not known to be exploited · fixed in d55c0c19b0d1f5c0101f9aa3b60534b6d6e11052 : 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 d55c0c19b0d1f5c0101f9aa3b60534b6d6e11052, 520b48753e3c54172a078e7e4b82aec83ae2e08d, 83d0d5e0ca22233c75daf139ec0063b9d2ff1ac7

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 d55c0c19b0d1f5c0101f9aa3b60534b6d6e11052, 520b48753e3c54172a078e7e4b82aec83ae2e08d or 83d0d5e0ca22233c75daf139ec0063b9d2ff1ac7.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 0a4b92c05ed02ad7abdd165823eaf4bbcb33ae5c, < d55c0c19b0d1f5c0101f9aa3b60534b6d6e11052
Fixed in
  • d55c0c19b0d1f5c0101f9aa3b60534b6d6e11052
LinuxLinuxAffected
  • ≥ 0a4b92c05ed02ad7abdd165823eaf4bbcb33ae5c, < 520b48753e3c54172a078e7e4b82aec83ae2e08d
Fixed in
  • 520b48753e3c54172a078e7e4b82aec83ae2e08d
LinuxLinuxAffected
  • ≥ 0a4b92c05ed02ad7abdd165823eaf4bbcb33ae5c, < 83d0d5e0ca22233c75daf139ec0063b9d2ff1ac7
Fixed in
  • 83d0d5e0ca22233c75daf139ec0063b9d2ff1ac7
LinuxLinuxAffected
  • =2.6.16
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: validate NT transaction response layout and offsets validate_ntransact() assumes that the response uses the fixed 18-word NT transaction layout. A different WordCount makes get_bcc() locate the byte count at a different offset from pSMBr->ByteCount, allowing the subsequent bounds checks to use inconsistent response boundaries. The function also turns the 32-bit ParameterOffset and DataOffset fields into pointers before checking their bounds. On a 32-bit client, a large offset can wrap the pointer below end_of_smb and pass the one-sided pointer comparison. The caller then dereferences the parameter pointer or copies from the data pointer. Require the expected WordCount before reading the byte count. Check each offset and count against the received SMB length as integers before forming either pointer. Use subtraction after validating the offset so that the range checks cannot overflow.

References

Community reviews

Loading reviews…