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-2023-52757smb: client: fix potential deadlock when releasing mids

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix potential deadlock when releasing mids All release_mid() callers seem to hold a reference of @mid so there is no need to call kref_put(&mid->refcount, __release_mid) under @server->mid_lock spinlock. If they don't, then an use-after-free bug would have occurred anyways. By getting rid of such spinlock also fixes a potential deadlock as shown below CPU 0 CPU 1 ------------------------------------------------------------------ cifs_demultiplex_thread() cifs_debug_data_proc_show() release_mid() spin_lock(&server->mid_lock); spin_lock(&cifs_tcp_ses_lock) spin_lock(&server->mid_lock) __release_mid() smb2_find_smb_tcon() spin_lock(&cifs_tcp_ses_lock) *deadlock*

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 years 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

CVSS scores of CVE-2023-52757, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.19% · top 92% of all CVEs (19 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 7b71843fa7028475b052107664cbe120156a2cfc – < 99f476e27aad5964ab13777d84fda67d1356dec1
    • affected 7b71843fa7028475b052107664cbe120156a2cfc – < ce49569079a9d4cad26c0f1d4653382fd9a5ca7a
    • affected 7b71843fa7028475b052107664cbe120156a2cfc – < 9eb44db68c5b7f5aa22b8fc7de74a3e2e08d1f29
    • affected 7b71843fa7028475b052107664cbe120156a2cfc – < b9bb9607b1fc12fca51f5632da25b36975f599bf
    • affected 7b71843fa7028475b052107664cbe120156a2cfc – < c1a5962f1462b64fe7b69f20a4b6af8067bc2d26
    • affected 7b71843fa7028475b052107664cbe120156a2cfc – < e6322fd177c6885a21dd4609dc5e5c973d1a2eb7
    • affected 9871dea42034ee6e73bb2b97ba0284d3d462b230
    • affected 5.4.6 – < 5.5
  • Linux · Linux

    • affected 5.5
    • unaffected < 5.5
    • unaffected 5.10.237 – ≤ 5.10.*
    • unaffected 5.15.181 – ≤ 5.15.*
    • unaffected 6.1.64 – ≤ 6.1.*
    • unaffected 6.5.13 – ≤ 6.5.*
    • unaffected 6.6.3 – ≤ 6.6.*
    • unaffected 6.7 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .