# CVE-2026-99279: ksmbd: reclaim ended sessions on logoff and expiration

Status: published. Published: 2026-11-07. Updated: 2026-11-07.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ d7fd1f98607f2cd358e583f9548bdf0173090a86; < 1767a5e45dbf6a3b12105196dda4fb0ef80b9698 (affected, git); ≥ d7fd1f98607f2cd358e583f9548bdf0173090a86; < 26534ef335e92b028eb58e44d98d46a0e26af0ec (affected, git); c99ea7855124ca1428a1e59c2b4590aaef34eacf (affected, git); ≥ 7.2.8; < 7.3 (affected, semver). Source: CNA: Linux
- Linux / Linux: 7.3 (affected); ≥ 0; < 7.3 (unaffected, semver); ≥ 7.3.2; ≤ 7.3.* (unaffected, semver); ≥ 7.4-rc1; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/1767a5e45dbf6a3b12105196dda4fb0ef80b9698 (CNA: Linux)

- https://git.kernel.org/stable/c/26534ef335e92b028eb58e44d98d46a0e26af0ec (CNA: Linux)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99279; retrieved 2026-11-07; source updated 2026-11-07

Revision: e077a070c364fafdaff18ec8688a98ebc399e5862d65f03a96408949a2adb27f

Canonical: https://y2.dev/cve/CVE-2026-99279

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.