CVE-2026-43377: ksmbd: Don't log keys in SMB3 signing and encryption key generation
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: Don't log keys in SMB3 signing and encryption key generation
When KSMBDDEBUGAUTH logging is enabled, generatesmb3signingkey() and generatesmb3encryptionkey() log the session, signing, encryption, and decryption key bytes. Remove the logs to avoid exposing credentials.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Disable KSMBD_DEBUG_AUTH logging to prevent ksmbd from logging session, signing, and encryption key bytes during SMB3 key generation.
Linux kernel ksmbd (KSMBD_DEBUG_AUTH) KSMBD_DEBUG_AUTH logging = disabled - Operational
Remove/clear the existing logs to avoid exposing any credentials/keys that may have been recorded while KSMBD_DEBUG_AUTH logging was enabled.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43377?
CVE-2026-43377 has a severity rating of 8.1, classified as high.
How do I fix CVE-2026-43377?
To fix CVE-2026-43377, ensure that you disable KSMBD_DEBUG_AUTH logging or upgrade to the patched version of the Linux kernel.
What systems are affected by CVE-2026-43377?
CVE-2026-43377 affects the Linux kernel, specifically through the ksmbd implementation.
What impact does CVE-2026-43377 have on security?
CVE-2026-43377 could lead to the exposure of sensitive session keys if debug logging is enabled.
When was CVE-2026-43377 published?
CVE-2026-43377 was published on May 8, 2026.