CVE-2025-68806: ksmbd: fix buffer validation by including null terminator size in EA length
In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix buffer validation by including null terminator size in EA length
The smb2_set_ea function, which handles Extended Attributes (EA),
was performing buffer validation checks that incorrectly omitted the size
of the null terminating character (+1 byte) for EA Name.
This patch fixes the issue by explicitly adding '+ 1' to EaNameLength where
the null terminator is expected to be present in the buffer, ensuring
the validation accurately reflects the total required buffer size.
Security readout for executives and security teams
Plain-English summary
A remotely reachable flaw in Linux's ksmbd SMB server miscalculates an extended-attribute name buffer by one byte. The supplied CVSS assessment indicates possible unauthorized disclosure without authentication or user interaction. Systems are exposed only when they run an affected kernel and use ksmbd on an attacker-reachable network.
Executive priority
Treat as a high-priority patching item for internet-facing or broadly reachable ksmbd servers. Accelerate inventory and compensating controls because authentication is not required under the supplied CVSS assessment. Lower the priority for hosts that do not use ksmbd, while still confirming distributor package status.
Technical view
The smb2_set_ea validation omitted the required null terminator when calculating the EA name's buffer length. The correction adds one byte to EaNameLength where termination is expected. The supplied record rates this CVSS 3.1 score 7.5 with network access, low complexity, no privileges, no interaction, and high confidentiality impact.
Likely exposure
Prioritize Linux hosts running an affected kernel where ksmbd is enabled and SMB is reachable from untrusted networks. The supplied status data identifies affected releases and commit identifiers, but package-level exposure may differ because distributors commonly backport kernel fixes.
Exploitation context
The supplied record is not in KEV and provides no evidence of active exploitation or a public exploit. Its CVSS vector nevertheless describes unauthenticated network reachability and low attack complexity. The exact disclosure mechanism and practical reliability are not established by the provided sources.
Researcher notes
The documented defect is an off-by-one validation error at an EA name boundary: validation excluded the null terminator expected in the input buffer. The sources establish the corrected calculation but do not identify a CWE, demonstrate exploitation, or fully explain how the stated high-confidentiality impact is achieved.
Mitigation direction
Apply a vendor-supported kernel update incorporating the applicable cited stable fix.
Consult the Linux distributor's advisory to map backported fixes to installed package versions.
Disable ksmbd where it is not operationally required.
Restrict SMB access to trusted networks until remediation is confirmed.
Validation and detection
Inventory kernel builds on systems that provide SMB through ksmbd.
Confirm whether ksmbd is enabled and reachable from untrusted network segments.
Check vendor package changelogs for CVE-2025-68806 or an applicable cited fix commit.
Verify the updated kernel is running after installation and reboot.
Reassess SMB exposure after remediation without sending malformed traffic.
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-68806 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.