CVE-2025-22043: ksmbd: add bounds check for durable handle context
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: add bounds check for durable handle context
Add missing bounds check for durable handle context.
Security readout for executives and security teams
Plain-English summary
Linux's in-kernel SMB server, ksmbd, failed to verify the size of durable-handle context data. A low-privileged remote user could potentially trigger unintended kernel access, risking sensitive-data exposure or service disruption. Systems not using ksmbd are unlikely to be exposed through this flaw.
Executive priority
Prioritize internet-facing or broadly reachable ksmbd servers for immediate assessment and patching. Schedule other affected SMB servers urgently based on access controls and business criticality. Systems demonstrably not using ksmbd can receive lower operational priority after that condition is documented.
Technical view
CVE-2025-22043 adds a missing bounds check while ksmbd processes durable-handle context. Its CVSS 3.1 score is 8.1: network reachable, low complexity, low privileges, no user interaction, with potentially high confidentiality and availability impact but no stated integrity impact.
Likely exposure
Exposure requires an affected Linux kernel with ksmbd present and processing SMB requests. Risk is greatest where the SMB service is reachable by untrusted or minimally privileged users. The supplied affected-version metadata is ambiguous, so determine exposure using distribution advisories, package changelogs, and the listed stable-kernel fixes.
Exploitation context
The supplied record does not establish public exploitation or a working exploit, and the CVE is not marked as CISA KEV. Its network vector, low complexity, and low privilege requirement make prompt assessment appropriate. Absence from KEV does not prove exploitation is impossible or absent.
Researcher notes
The source describes only a missing bounds check and supplies no CWE, crash trace, proof of concept, or exploitation evidence. CVSS indicates confidentiality and availability consequences, but the exact failure mode is not documented here. Multiple stable commits likely correspond to kernel branches; branch mapping should be confirmed before declaring a system fixed.
Mitigation direction
Install the distribution or vendor kernel update that incorporates the applicable stable-kernel fix.
If immediate updating is impossible, restrict SMB access to trusted users and networks.
Disable ksmbd where it is not operationally required, following vendor guidance.
Reboot into the corrected kernel and remove obsolete vulnerable kernels according to operational policy.
Validation and detection
Confirm whether ksmbd is installed, loaded, enabled, or configured to start.
Identify the running kernel version and distribution package release.
Check vendor advisories or package changelogs for explicit CVE-2025-22043 remediation.
Verify the installed kernel contains the applicable listed stable-kernel commit.
Confirm SMB exposure is limited to intended network segments and authenticated users.
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-22043 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
0ADP providers
6Source 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.