cve.bz

CVE-2026-99277

no score yet

No CVSS score yet.

In the Linux kernel, the following vulnerability has been resolved: ksmbd: hold a connection reference for each session channel ksmbd_session_unregister() removes a session from the global and per- connection tables before dropping the table reference. A concurrent reference holder can keep the session and its channel list alive after those removals. Connection cleanup can no longer find the unpublished session to remove its channels. Since a channel only stores a raw conn pointer, the connection can be freed while another session reference holder is still accessing it, for example during SMB3.1.1 binding or a procfs read. Take a connection reference when registering a channel and release it on insertion failure, channel removal, or final session destruction. Keep the channels and signing keys until the session is destroyed so a response can still be signed after the session has been unregistered.
Published
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-99277 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99277?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99277?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-99277 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Versions

From the CNA's record in the CVE List.

ProductAffected
Linuxfrom 7.2.8 before 7.3
Linux7.3 and later

Fixed in

ProductRelease lineFixed in
Linux7.37.3.2
Linuxlater releases7.4-rc1

References

Check your stackJSON