CVE-2026-72492: ksmbd: fix use-after-free in same_client_has_lease()
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.64% (FIRST EPSS); higher than 51.2% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 09634cd055d9bd8dd167995ea52bcd8028dd5dac, 0ff82a9cf9312678d8bc4edeef0b6e82659ac12a, 35d3d6ff2bc1e7aaecb15d5377ebbd6227acae0d.
Low priority for now. Upgrade to Linux Linux 09634cd055d9bd8dd167995ea52bcd8028dd5dac, 0ff82a9cf9312678d8bc4edeef0b6e82659ac12a, 35d3d6ff2bc1e7aaecb15d5377ebbd6227acae0d or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix use-after-free in same_client_has_lease() same_client_has_lease() returns an opinfo pointer from ci->m_op_list after dropping ci->m_lock without taking a reference. smb_grant_oplock() then dereferences that pointer in copy_lease() and when checking breaking_cnt. A concurrent close can remove the old lease from ci->m_op_list and drop the last reference before the caller uses the returned pointer, leading to a use-after-free. Take a reference when same_client_has_lease() selects an existing lease, drop any previous match while scanning, and release the returned reference in smb_grant_oplock() after copying the lease state.
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.6% · 51th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.15affected
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before aaa3bb2bbf2ccbfea9e4e0b9dabf3afc60b50cd0affected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before 09634cd055d9bd8dd167995ea52bcd8028dd5dacaffected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before 7c3264d273d524aa6adcce23c01087271f13586faffected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before 79c7c59bb519db6f5a2a151965e825ec725614ccaffected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before 35d3d6ff2bc1e7aaecb15d5377ebbd6227acae0daffected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before 0ff82a9cf9312678d8bc4edeef0b6e82659ac12aaffected · git
- e2f34481b24db2fd634b5edb0a5bd0e4d38cc6e9 and later · before 65b655f65c3ca1ab5d598d3832bb0ff531725858affected · git
- before 5.15not affected · semver
- 5.15.212 and later · up to and including 5.15.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72489Aug 15, 2026 · staging: nvec: fix use-after-free in nvec_rx_completed()33Monitor
- ← EarlierCVE-2026-72490Aug 15, 2026 · staging: rtl8723bs: fix stainfo check in rtw_aes_decrypt0Monitor
- Later →CVE-2026-72498Aug 15, 2026 · RDMA/bnxt_re: Avoid displaying the kernel pointer0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 09634cd055d9bd8dd167995ea52bcd8028dd5dac | Vendor (CNA) |
| Linux Linux | 0ff82a9cf9312678d8bc4edeef0b6e82659ac12a | Vendor (CNA) |
| Linux Linux | 35d3d6ff2bc1e7aaecb15d5377ebbd6227acae0d | Vendor (CNA) |
| Linux Linux | 65b655f65c3ca1ab5d598d3832bb0ff531725858 | Vendor (CNA) |
| Linux Linux | 79c7c59bb519db6f5a2a151965e825ec725614cc | Vendor (CNA) |
| Linux Linux | 7c3264d273d524aa6adcce23c01087271f13586f | Vendor (CNA) |
| Linux Linux | aaa3bb2bbf2ccbfea9e4e0b9dabf3afc60b50cd0 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/0ff82a9cf9312678d8bc4edeef0b6e82659ac12a
- git.kernel.org/stable/c/35d3d6ff2bc1e7aaecb15d5377ebbd6227acae0d
- git.kernel.org/stable/c/65b655f65c3ca1ab5d598d3832bb0ff531725858
- git.kernel.org/stable/c/79c7c59bb519db6f5a2a151965e825ec725614cc
- git.kernel.org/stable/c/7c3264d273d524aa6adcce23c01087271f13586f
- git.kernel.org/stable/c/aaa3bb2bbf2ccbfea9e4e0b9dabf3afc60b50cd0
Vendor advisories and official records. Exploit/PoC links are deliberately left out.