CVE-2026-98172
smb: client: fix smbd_connection leak on cifs_get_tcp_session() error
No known exploitation. EPSS puts it in the 6th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 2f8946464b11822169b9f10c7cf58a2440b51d54, < 3164402c58940ff58a3cecdb026405f07b0253afUpgrade to: 3164402c58940ff58a3cecdb026405f07b0253afAffected: ≥ 2f8946464b11822169b9f10c7cf58a2440b51d54, < e3344bb0ff5ec8a276f42239e140f5442841ef23Upgrade to: e3344bb0ff5ec8a276f42239e140f5442841ef23Affected: ≥ 2f8946464b11822169b9f10c7cf58a2440b51d54, < 5c908e49d349266dff0c86dda6a05df0ff19b824Upgrade to: 5c908e49d349266dff0c86dda6a05df0ff19b824Affected: ≥ 2f8946464b11822169b9f10c7cf58a2440b51d54, < 928edc4bd6a617caabeb575fc13c254d9df623c4Upgrade to: 928edc4bd6a617caabeb575fc13c254d9df623c4 + 2 more branchesStated 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: smb: client: fix smbd_connection leak on cifs_get_tcp_session() error When an RDMA connection is successfully established via smbd_get_connection() but cifs_get_tcp_session() later fails (e.g. kthread_create() returns an error), the error path frees tcp_ses without first destroying the smbd_connection. Fix this by calling smbd_destroy() in the out_err cleanup path before kfree(tcp_ses). smbd_destroy() safely handles the case where smbd_conn is NULL, so it can be called unconditionally.
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
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 6th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/3164402c58940ff58a3cecdb026405f07b0253af
- git.kernel.org/stable/c/e3344bb0ff5ec8a276f42239e140f5442841ef23
- git.kernel.org/stable/c/5c908e49d349266dff0c86dda6a05df0ff19b824
And 3 more references. See all after sign-in
In the news
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