SMB3 session-key disclosure via authentication debug logging
Published May 8, 2026 · Updated May 8, 2026
Information disclosure in ksmbd in Linux Kernel allows remote authenticated users to expose SMB3 session keys via SMB3 session setup. generate_smb3signingkey() and generate_smb3encryptionkey() write session, signing, encryption, and decryption key bytes to kernel logs instead of excluding that material from diagnostic output. The leak requires KSMBD_DEBUG_AUTH logging and an authenticated SMB3 session with signing or encryption, exposing protected traffic without directly affecting availability.
Summary
What happened
Information disclosure in ksmbd in Linux Kernel allows remote authenticated users to expose SMB3 session keys via SMB3 session setup. generate_smb3signingkey() and generate_smb3encryptionkey() write session, signing, encryption, and decryption key bytes to kernel logs instead of excluding that material from diagnostic output. The leak requires KSMBD_DEBUG_AUTH logging and an authenticated SMB3 session with signing or encryption, exposing protected traffic without directly affecting availability.
The record
- CVE
- CVE-2026-43377
- Published
- May 8, 2026
- Updated
- May 8, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 8, 2026CVE publishedPublication date reported by the CVE source.
- May 8, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.15
- Affected versionversion=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <3fe2d9ec166b7df9a8df6c0fdcfc210572e27e3f
- Affected versionversion=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <407cc37c21d51f9b9d4d20204b04890880cfa6ae
- Affected versionversion=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <4084ed720d7d5f4e975c9e4a6267a552dad3b24a
- Affected versionversion=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <441336115df26b966575de56daf7107ed474faed
- Affected versionversion=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <c6b01b997a2094969e315f1ebfc1d64b8ae2163d
- Affected versionversion=e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 <fec5c70b82af3f59f15bb984df94e5ad1fccfb1e
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo