Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98420ksmbd: 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.

Timeline

  1. ID reserved

    By Linux

  2. · 19 days later

    Published

  3. · 5 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected ea174a91893956450510945a0c5d1a10b5323656 – < c99ea7855124ca1428a1e59c2b4590aaef34eacf
    • affected ea174a91893956450510945a0c5d1a10b5323656 – < d7fd1f98607f2cd358e583f9548bdf0173090a86
    • affected a6a9601ba995d0fec635324cb9fd8d14f9bea14e
    • affected 1fc8a2b14ef5223f8e0b95faba2ee0a6e4d0f99d
    • affected 750a2d772e9d9ff377fd32e3b6797bf2cd847a7a
    • affected 6775ee7ef4b37c521aa4cf3730f54554c4875542
    • affected 5.15.145 – < 5.16
    • affected 6.1.29 – < 6.2
    • affected 6.2.16 – < 6.3
    • affected 6.3.2 – < 6.4
  • Linux · Linux

    • affected 6.4
    • unaffected < 6.4
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References2

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98420 badge
[![CVE-2026-98420](https://cveledger.app/badge/CVE-2026-98420.svg)](https://cveledger.app/cve/CVE-2026-98420)

Record last updated .