Linux
smb: client: fix create context out-of-bounds reads
In the Linux kernel, the following vulnerability has been resolved: smb: client: fix create context out-of-bounds reads smb2_parse_contexts() validates the complete create-context area but does not limit each record to its Next field before dispatching it. A malformed chain can therefore expose bytes beyond the current context to a handler. The QFid handler also used a full response-structure cast although it only reads DiskFileId. The SMB2/SMB3 lease parsers made the same layout assumption: they read LeaseState and LeaseFlags at canonical offsets rather than at DataOffset. A valid non-canonical DataOffset could therefore yield unrelated in-bounds data, while a short DataLength was still accepted. Limit each context to its Next value, reject offsets before the context header, and reject malformed chains. Bound the name range by the current context and do not dispatch a known handler when DataLength is zero. Read the QFid DiskFileId only when the context data covers that field. Parse the lease context from DataOffset and require DataLength to match the v1 or v2 lease_context size used by ksmbd. A size mismatch skips lease parsing without failing the open.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= b8c32dbb0deb287a5fcb78251e4eae6c7275760d, < 34245048d6c1fa6d7be4f0dec1d14b5be02360e1
- >= b8c32dbb0deb287a5fcb78251e4eae6c7275760d, < 0a8c2a6715c2a67b7abbbf874fccc9f5518146d9
- >= b8c32dbb0deb287a5fcb78251e4eae6c7275760d, < 43d0ca48bb902d554b6531862248810d2ae3b8ef
- >= b8c32dbb0deb287a5fcb78251e4eae6c7275760d, < e4c49012708c917eafd9c27054b02d0f8b30fe64
- >= b8c32dbb0deb287a5fcb78251e4eae6c7275760d, < 28bc9a871799363afa3139e961a8e3684feb8704
- >= b8c32dbb0deb287a5fcb78251e4eae6c7275760d, < 05a7fd80024ff32b9b40ab1478bb172eeab1c386
- >= b8c32dbb0deb287a5fcb78251e4eae6c7275760d, < cecc5399987e73a528ce2b662eeb54af69163cbd
- >= b8c32dbb0deb287a5fcb78251e4eae6c7275760d, < 67f4c1c6a1b51e203d986779299824d1c2c590a6
Fixed in 34245048d6c1fa6d7be4f0dec1d14b5be02360e1, 0a8c2a6715c2a67b7abbbf874fccc9f5518146d9, 43d0ca48bb902d554b6531862248810d2ae3b8ef, e4c49012708c917eafd9c27054b02d0f8b30fe64, 28bc9a871799363afa3139e961a8e3684feb8704, 05a7fd80024ff32b9b40ab1478bb172eeab1c386, cecc5399987e73a528ce2b662eeb54af69163cbd, 67f4c1c6a1b51e203d986779299824d1c2c590a6
- 3.7
Fixed in 0, 5.10.273, 5.15.224, 6.1.191, 6.6.158, 6.12.112, 6.18.55, 7.2.9, 7.3
Mitigation
Upgrade Linux to 34245048d6c1fa6d7be4f0dec1d14b5be02360e1 or 0a8c2a6715c2a67b7abbbf874fccc9f5518146d9 or 43d0ca48bb902d554b6531862248810d2ae3b8ef or e4c49012708c917eafd9c27054b02d0f8b30fe64 or 28bc9a871799363afa3139e961a8e3684feb8704 or 05a7fd80024ff32b9b40ab1478bb172eeab1c386 or cecc5399987e73a528ce2b662eeb54af69163cbd or 67f4c1c6a1b51e203d986779299824d1c2c590a6 or later.
Upgrade Linux to 0 or 5.10.273 or 5.15.224 or 6.1.191 or 6.6.158 or 6.12.112 or 6.18.55 or 7.2.9 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.