Skip to main content
← Vulnerabilities

ksmbd: reclaim ended sessions on logoff and expiration

Exploited
No known exploitation
Fix
Fixed in 7.3
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 7.3.

Published
Last modified
20/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

The ksmbd SMB server in the Linux kernel can keep ended sessions in memory after logoff or session replacement, so memory and connection slots are not released. The fix reclaims these ended sessions in the expiration worker and keeps sessions with expired Kerberos credentials available for reauthentication.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: reclaim ended sessions on logoff and expiration

LOGOFF and previous-session replacement leave sessions Expired with a zero credential expiry. Ended sessions can retain their memory and connection slots when no further setup arrives on the owning connection.

Unpublish a logged-off session while the request reference keeps its response signing and encryption keys alive. Remove its procfs entry before dropping the table reference so a reader cannot remove its own entry on the last put. Clear proc_entry after removal to avoid removing it twice.

Reclaim ended sessions from the global table in the existing expiration worker before it acquires conn_list_lock. Only select Expired sessions with zero credential expiry and no references beyond the table reference. Keep sessions whose Kerberos credentials expired available for reauthentication.

Unlink the session from its setup connection and all channel connections, so SMB2 sessions and sessions with only secondary SMB3 channels are covered. The session already holds connection references, and sessions_table_lock prevents concurrent channel removal. Queue sessions on a separate disposal list, leaving their hash nodes unhashed, and remove procfs entries and drop table references outside the locks.

Keep the pending setup check before allocating a new session so abandoned InProgress sessions can release their slots even at the connection limit. Retain the timeout and reference checks and dispose of those sessions outside the locks. Leave ended Expired sessions to the expiration worker.

cve.now Index

20Pcve.now Index 20 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 7.3.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Linux Linux

    From 7.2.8 · fixed in 7.3

  • Linux Linux

    7.3

Evidence 2

  1. Link
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-99279

Is CVE-2026-99279 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-99279?

Linux: from 7.2.8 before 7.3. Linux: version 7.3.Source: cve.now feed data

How do I fix CVE-2026-99279?

Upgrade to a fixed version: 7.3.Source: cve.now feed data