In the Linux kernel, the following vulnerability has been resolved: ksmbd: defer connection scavenging while session locks are busy The…
CVE-2026-99276
In the Linux kernel, the following vulnerability has been resolved: ksmbd: defer connection scavenging while session locks are busy The expiration worker holds connlistlock for reading while checking for authenticated sessions. Without this change, the check can wait for conn->sessionlock or sessionstablelock. In destroyprevioussession(), the status updates after ksmbdconnwaitidlesess() run with both session locks held for writing. Both the KSMBDSESSGOOD error path and the KSMBDSESSNEEDSETUP success path call ksmbdallconnsetstatus(), which takes connlistlock for reading. A writer queued on connlistlock can block these new read acquisitions. The worker then waits for a session lock held by destroyprevioussession(), which waits behind the writer. The writer cannot proceed until the worker releases connlistlock. 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.
Assessment
- CVSS
- Not yet scored
- Severity
- Unscored
- Known exploited
- Not listed in CISA KEV
- Exploit availability
- Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
- Published
- 7 November 2026
- Last updated
- 7 November 2026
- Assigner
- Linux
At the source
References
Community proofs of concept
No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.
Submit a proof of concept
Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.
Query this programmatically
Agents can read this through the MCP endpoint, or over HTTP:
curl https://cve.zerocrew.in/api/cve/CVE-2026-99276