CVE-2026-98420ksmbd: follow SMB2 session expiration semantics
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 14, 2026
- First seen by InfoSec Signals
- Oct 14, 2026
Affected products
Linux Linux linux:linux (from the name) | from ea174a91893956450510945a0c5d1a10b5323656 before c99ea7855124ca1428a1e59c2b4590aaef34eacf; from ea174a91893956450510945a0c5d1a10b5323656 before d7fd1f98607f2cd358e583f9548bdf0173090a86; a6a9601ba995d0fec635324cb9fd8d14f9bea14e; 1fc8a2b14ef5223f8e0b95faba2ee0a6e4d0f99d; 750a2d772e9d9ff377fd32e3b6797bf2cd847a7a; 6775ee7ef4b37c521aa4cf3730f54554c4875542; from 5.15.145 before 5.16; from 6.1.29 before 6.2; and 2 more ranges | CNA record |
References
- https://git.kernel.org/stable/c/c99ea7855124ca1428a1e59c2b4590aaef34eacf
- https://git.kernel.org/stable/c/d7fd1f98607f2cd358e583f9548bdf0173090a86
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.