CVE-2026-99277
ksmbd: hold a connection reference for each session channel
No known exploitation. No EPSS score yet. Fixed versions are out.
No public exploit knownFix1 product3 fixed builds listed below
No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ d7fd1f98607f2cd358e583f9548bdf0173090a86, < 4b333aed69cfc2c8687b86b6a4364a0dffc16dd8Upgrade to: 4b333aed69cfc2c8687b86b6a4364a0dffc16dd8Affected: ≥ d7fd1f98607f2cd358e583f9548bdf0173090a86, < add8d7fb04efe564193df73581889c62fc0016f1Upgrade to: add8d7fb04efe564193df73581889c62fc0016f1Affected: c99ea7855124ca1428a1e59c2b4590aaef34eacfUpgrade to: not statedAffected: ≥ 7.2.8, < 7.3Upgrade to: 7.3Stated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
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.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
No EPSS score yet. New CVEs are usually scored within a few days.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI