CVE-2025-38527 — smb: client: fix use-after-free in cifs_oplock_break
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.4% (30-day exploitation probability)+5
- Technical severity (high)+6
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Debian | Debian Linux | version 11.0 | Vulnerable | NIST National Vulnerability Database |
| Linux | Linux |
version 53fc31a4853e30d6e8f142b824f724da27ff3e40≥ b98749cac4a695f084a5ff076f4510b23e353ecd and < 4256a483fe58af66a46cbf3dc48ff26e580d3308≥ b98749cac4a695f084a5ff076f4510b23e353ecd and < 0a4eec84d4d2c4085d4ed8630fd74e4b39033c1b≥ b98749cac4a695f084a5ff076f4510b23e353ecd and < 2baaf5bbab2ac474c4f92c10fcb3310f824db995≥ b98749cac4a695f084a5ff076f4510b23e353ecd and < 09bce2138a30ef10d8821c8c3f73a4ab7a5726bc≥ b98749cac4a695f084a5ff076f4510b23e353ecd and < da11bd4b697b393a207f19a2ed7d382a811a3ddc≥ b98749cac4a695f084a5ff076f4510b23e353ecd and < 705c79101ccf9edea5a00d761491a03ced314210version 2429fcf06d3cb962693868ab0a927c9038f12a2d and 9 moreversion 1ee4f2d7cdcd4508cc3cbe3b2622d7177b89da12version 8092ecc306d81186a64cda42411121f4d35aaff4version ebac4d0adf68f8962bd82fcf483936edd6ec095b≥ 3.16.72 and < 3.17≥ 4.9.171 and < 4.10≥ 4.14.114 and < 4.15≥ 4.19.37 and < 4.20≥ 5.0.10 and < 5.1version 5.1 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel |
version 6.16-rc5≥ 6.7 and < 6.12.40≥ 3.16.72 and < 3.17≥ 4.9.171 and < 4.10≥ 4.14.114 and < 4.15≥ 4.19.37 and < 4.20≥ 5.0.10 and < 5.1≥ 5.1.1 and < 5.15.190 and 11 more≥ 5.16 and < 6.1.147≥ 6.2 and < 6.6.100version 6.16-rc6≥ 6.13 and < 6.15.8version 5.1version 5.1-rc6version 5.1-rc7version 6.16-rc1version 6.16-rc2version 6.16-rc3version 6.16-rc4 |
Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.8 | CVSS 3.1 | Critical | 3.9 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 9.8 | CVSS 3.1 | Critical | — | — | Linux via CVE Program (cve.org) e CISA ADP |
| 7.8 | CVSS 3.1 | High | 1.8 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 7.8 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · linux/linux kernel, debian/debian linux
- CVSS changed · 7.8
- Source status changed · → Modified
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 15, 2026 – Oct 15, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
9 on the record
- git.kernel.org/stable/c/2baaf5bbab2ac474c4f92c10fcb3310f824db995
- git.kernel.org/stable/c/4256a483fe58af66a46cbf3dc48ff26e580d3308
- git.kernel.org/stable/c/0a4eec84d4d2c4085d4ed8630fd74e4b39033c1b
- git.kernel.org/stable/c/09bce2138a30ef10d8821c8c3f73a4ab7a5726bc
- git.kernel.org/stable/c/705c79101ccf9edea5a00d761491a03ced314210
- git.kernel.org/stable/c/da11bd4b697b393a207f19a2ed7d382a811a3ddc
- nvd.nist.gov/vuln/detail/CVE-2025-38527
- github.com/advisories/GHSA-hm6q-hprh-4f22
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 1d
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 1d
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-38527 is "smb: client: fix use-after-free in cifs_oplock_break", rated High. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 0.41% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.