ksmbd: follow SMB2 session expiration semantics
Summary
| CVE | CVE-2026-98420 |
|---|
| State | PUBLISHED |
|---|
| Assigner | Linux |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2026-10-14 14:17:53 UTC |
|---|
| Updated | 2026-10-14 14:17:53 UTC |
|---|
| 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. |
|---|
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected ea174a91893956450510945a0c5d1a10b5323656 c99ea7855124ca1428a1e59c2b4590aaef34eacf git |
Not specified |
| CNA |
Linux |
Linux |
affected ea174a91893956450510945a0c5d1a10b5323656 d7fd1f98607f2cd358e583f9548bdf0173090a86 git |
Not specified |
| CNA |
Linux |
Linux |
affected a6a9601ba995d0fec635324cb9fd8d14f9bea14e git |
Not specified |
| CNA |
Linux |
Linux |
affected 1fc8a2b14ef5223f8e0b95faba2ee0a6e4d0f99d git |
Not specified |
| CNA |
Linux |
Linux |
affected 750a2d772e9d9ff377fd32e3b6797bf2cd847a7a git |
Not specified |
| CNA |
Linux |
Linux |
affected 6775ee7ef4b37c521aa4cf3730f54554c4875542 git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.15.145 5.16 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.1.29 6.2 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.2.16 6.3 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.3.2 6.4 semver |
Not specified |
| CNA |
Linux |
Linux |
affected 6.4 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.4 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.2.8 7.2.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.3-rc4 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/c99ea7855124ca1428a1e59c2b4590aaef34eacf |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/d7fd1f98607f2cd358e583f9548bdf0173090a86 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.