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-2025-38527smb: client: fix use-after-free in cifs_oplock_break

Description

In the Linux kernel, the following vulnerability has been resolved: smb: client: fix use-after-free in cifs_oplock_break A race condition can occur in cifs_oplock_break() leading to a use-after-free of the cinode structure when unmounting: cifs_oplock_break() _cifsFileInfo_put(cfile) cifsFileInfo_put_final() cifs_sb_deactive() [last ref, start releasing sb] kill_sb() kill_anon_super() generic_shutdown_super() evict_inodes() dispose_list() evict() destroy_inode() call_rcu(&inode->i_rcu, i_callback) spin_lock(&cinode->open_file_lock) <- OK [later] i_callback() cifs_free_inode() kmem_cache_free(cinode) spin_unlock(&cinode->open_file_lock) <- UAF cifs_done_oplock_break(cinode) <- UAF The issue occurs when umount has already released its reference to the superblock. When _cifsFileInfo_put() calls cifs_sb_deactive(), this releases the last reference, triggering the immediate cleanup of all inodes under RCU. However, cifs_oplock_break() continues to access the cinode after this point, resulting in use-after-free. Fix this by holding an extra reference to the superblock during the entire oplock break operation. This ensures that the superblock and its inodes remain valid until the oplock break completes.

Timeline

  1. ID reserved

    By Linux

  2. · 4 months later

    Published

  3. · 14 months 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-2025-38527, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.8CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.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.46% · top 60% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected b98749cac4a695f084a5ff076f4510b23e353ecd – < 4256a483fe58af66a46cbf3dc48ff26e580d3308
    • affected b98749cac4a695f084a5ff076f4510b23e353ecd – < 0a4eec84d4d2c4085d4ed8630fd74e4b39033c1b
    • affected b98749cac4a695f084a5ff076f4510b23e353ecd – < 2baaf5bbab2ac474c4f92c10fcb3310f824db995
    • affected b98749cac4a695f084a5ff076f4510b23e353ecd – < 09bce2138a30ef10d8821c8c3f73a4ab7a5726bc
    • affected b98749cac4a695f084a5ff076f4510b23e353ecd – < da11bd4b697b393a207f19a2ed7d382a811a3ddc
    • affected b98749cac4a695f084a5ff076f4510b23e353ecd – < 705c79101ccf9edea5a00d761491a03ced314210
    • affected 2429fcf06d3cb962693868ab0a927c9038f12a2d
    • affected 1ee4f2d7cdcd4508cc3cbe3b2622d7177b89da12
    • affected 53fc31a4853e30d6e8f142b824f724da27ff3e40
    • affected 8092ecc306d81186a64cda42411121f4d35aaff4
    • affected ebac4d0adf68f8962bd82fcf483936edd6ec095b
    • affected 3.16.72 – < 3.17
    • affected 4.9.171 – < 4.10
    • affected 4.14.114 – < 4.15
    • affected 4.19.37 – < 4.20
    • affected 5.0.10 – < 5.1
  • Linux · Linux

    • affected 5.1
    • unaffected < 5.1
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.147 – ≤ 6.1.*
    • unaffected 6.6.100 – ≤ 6.6.*
    • unaffected 6.12.40 – ≤ 6.12.*
    • unaffected 6.15.8 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .