CVE-2025-22042: ksmbd: add bounds check for create lease context
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: add bounds check for create lease context
Add missing bounds check for create lease context.
Security readout for executives and security teams
Plain-English summary
Linux’s ksmbd SMB server lacks a bounds check when handling a create lease context. A network user with limited privileges could potentially expose sensitive kernel memory or disrupt the server. Integrity impact is not indicated. Systems that do not use ksmbd have low direct exposure.
Executive priority
Expedite assessment and patching for SMB servers using ksmbd, particularly network-reachable systems. Potential confidentiality and availability impacts are substantial. The issue is high rather than critical because limited privileges are required and active exploitation is not established. Deprioritize non-ksmbd hosts only after confirming they are not exposed.
Technical view
CVE-2025-22042 affects ksmbd create lease context handling. The CVSS 8.1 vector indicates network access, low complexity, low privileges, no user interaction, high confidentiality impact, and high availability impact. The kernel fix adds the missing bounds check. The supplied sources do not describe the precise memory-access primitive.
Likely exposure
Exposure requires a Linux system running ksmbd and accepting reachable SMB requests. The bundle marks several 5.15-to-6.15-era kernel entries as affected, but does not provide clear range semantics. Distribution package versions and backports must therefore be checked against vendor guidance and the linked stable fixes.
Exploitation context
The bundle reports that this CVE is not in KEV and provides no evidence of active exploitation or a public proof of concept. CVSS indicates network reachability and low attack complexity, but also requires low privileges. These are scoring assumptions, not confirmation that reliable exploitation exists.
Researcher notes
The bundle provides minimal root-cause detail and several stable-kernel commits. It does not establish exact malformed-field mechanics, crash signatures, exploitation primitives, or unambiguous affected and fixed ranges. The version data includes an unexplained "0" and repeated commit identifiers, so branch status should be confirmed through patch ancestry and distribution advisories.
Mitigation direction
Install a distribution kernel update that incorporates the relevant linked Linux stable fix.
Reboot into the updated kernel and confirm the fixed kernel is running.
Check Linux and distribution advisories for exact fixed package versions and backport status.
Until updated, restrict SMB access to trusted networks and least-privileged accounts.
Disable ksmbd temporarily if it is unnecessary and operational policy permits.
Validation and detection
Inventory systems to determine whether ksmbd is installed, loaded, configured, and serving SMB traffic.
Compare each running kernel package and vendor backport status with the referenced stable fixes.
Confirm SMB access is not exposed beyond intended network and account trust boundaries.
After updating, verify the corrected kernel is running and normal ksmbd operations remain functional.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-22042 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
8Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.