Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98172smb: client: fix smbd_connection leak on cifs_get_tcp_session() error

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 24 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 2f8946464b11822169b9f10c7cf58a2440b51d54 – < c295f6505aec085d73e8dcea9f648c8af1b9da8c
    • affected 2f8946464b11822169b9f10c7cf58a2440b51d54 – < 45a97df1b7fe6c1ca5493f8fb5284203991aeeb9
    • affected 2f8946464b11822169b9f10c7cf58a2440b51d54 – < 3164402c58940ff58a3cecdb026405f07b0253af
    • affected 2f8946464b11822169b9f10c7cf58a2440b51d54 – < e3344bb0ff5ec8a276f42239e140f5442841ef23
    • affected 2f8946464b11822169b9f10c7cf58a2440b51d54 – < 5c908e49d349266dff0c86dda6a05df0ff19b824
    • affected 2f8946464b11822169b9f10c7cf58a2440b51d54 – < 928edc4bd6a617caabeb575fc13c254d9df623c4
    • affected 2f8946464b11822169b9f10c7cf58a2440b51d54 – < b26a3fcf2f1c2cadba400290b639f01395db8fc8
    • affected 2f8946464b11822169b9f10c7cf58a2440b51d54 – < e75c96157d45e498970158c8f7373d90102e33b9
  • Linux · Linux

    • affected 4.16
    • unaffected < 4.16
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.224 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98172 badge
[![CVE-2026-98172](https://cveledger.app/badge/CVE-2026-98172.svg)](https://cveledger.app/cve/CVE-2026-98172)

Record last updated .