CVE-2026-98420

ksmbd: follow SMB2 session expiration semantics

Description

In the Linux kernel, the following vulnerability has been resolved: ksmbd: follow SMB2 session expiration semantics ksmbd_session_register() destroys valid sessions after ten seconds of inactivity whenever a client starts another SessionSetup exchange. This confuses Session.IdleTime with Session.ExpirationTime. Windows can create additional authenticated sessions on an existing connection, so deleting the older session invalidates its tree connects and makes mapped drives fail with STATUS_NETWORK_NAME_DELETED. The session expiration rules require the server to change a valid session to expired only after its credential expiration time passes. A valid or expired session otherwise keeps its connection from being scavenged. Connections that have not negotiated a dialect, have no sessions, or have only InProgress sessions are disconnected after an implementation-specific timeout. Use the Windows-compatible 45 second value and run the expiration check periodically for both TCP and SMB Direct. Keep zero as an infinite credential expiration time, and count each Valid-to-Expired transition. Set expired sessions to InProgress when they reauthenticate. If authentication fails, remove the session from the global and per-connection tables immediately, including SMB3 multichannel connections. Retain protection against abandoned SessionId-zero exchanges by allowing only one InProgress authentication per connection. Additional exchanges fail with STATUS_INSUFFICIENT_RESOURCES, and stale InProgress sessions are reaped after the same 45 second setup timeout. This bounds the original unauthenticated memory-exhaustion path without evicting established sessions.

Key facts

Published
14 Oct 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.237% likely to be exploited in the next 30 days, higher than 14.902% of CVEs (scores for 18 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • ea174a91893956450510945a0c5d1a10b5323656 up to but excluding c99ea7855124ca1428a1e59c2b4590aaef34eacf (affected)
  • ea174a91893956450510945a0c5d1a10b5323656 up to but excluding d7fd1f98607f2cd358e583f9548bdf0173090a86 (affected)
  • a6a9601ba995d0fec635324cb9fd8d14f9bea14e (affected)
  • 1fc8a2b14ef5223f8e0b95faba2ee0a6e4d0f99d (affected)
  • 750a2d772e9d9ff377fd32e3b6797bf2cd847a7a (affected)
  • 6775ee7ef4b37c521aa4cf3730f54554c4875542 (affected)
  • 5.15.145 up to but excluding 5.16 (affected)
  • 6.1.29 up to but excluding 6.2 (affected)
  • 6.2.16 up to but excluding 6.3 (affected)
  • 6.3.2 up to but excluding 6.4 (affected)
LinuxLinux
  • Default status: affected
  • 6.4 (affected)
  • 0 up to but excluding 6.4 (unaffected)
  • 7.2.8 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 14 Oct 2026 Published

References