# CVE-2026-99276: ksmbd: defer connection scavenging while session locks are busy

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

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

ksmbd: defer connection scavenging while session locks are busy

The expiration worker holds conn_list_lock for reading while checking
for authenticated sessions. Without this change, the check can wait for
conn->session_lock or sessions_table_lock.

In destroy_previous_session(), the status updates after
ksmbd_conn_wait_idle_sess() run with both session locks held for
writing. Both the KSMBD_SESS_GOOD error path and the
KSMBD_SESS_NEED_SETUP success path call ksmbd_all_conn_set_status(),
which takes conn_list_lock for reading.

A writer queued on conn_list_lock can block these new read acquisitions.
The worker then waits for a session lock held by
destroy_previous_session(), which waits behind the writer. The writer
cannot proceed until the worker releases conn_list_lock.

Try both session locks instead of waiting in the scavenging check. Keep
the connection when either lock is busy and let the periodic worker
retry later.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ d7fd1f98607f2cd358e583f9548bdf0173090a86; < 4e4e8b38994a0b0fc23f00ca6698b469a41abe70 (affected, git); ≥ d7fd1f98607f2cd358e583f9548bdf0173090a86; < b4bae7af1154089be87c7475218264fcbfd16d10 (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/4e4e8b38994a0b0fc23f00ca6698b469a41abe70 (CNA: Linux)

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

## Provenance

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

Revision: 337f1bcff9245280d558110335b6d5d86f3338fbde2952240687ab0409ebd1b7

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

## 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.