VulnerabilityPublished 13 Jan 2026Updated 30 Jul 2026

CVE-2025-68806: Linux kernel · ksmbd: fix buffer validation by including null terminator size in EA length

Source GCVE Database

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 13:47 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-4wfq-6xp5-vp47

What to do

AI-suggested

Until a patch is available, cautious use of ksmbd or disabling it if not needed may reduce exposure.

Description

A vulnerability in the Linux kernel's ksmbd component related to buffer validation in the smb2_set_ea function has been resolved. The issue involved incorrect buffer size checks that omitted the null terminator byte for Extended Attribute (EA) names. This could lead to improper validation of buffer sizes when handling EA data.

Impact

The vulnerability affects the integrity of buffer validation in the ksmbd SMB2 Extended Attributes handling. According to the CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), it is remotely exploitable without privileges or user interaction and can lead to a high impact on confidentiality. There is no indication of impact on integrity or availability. No known exploits are reported in the wild.

Summary

The vulnerability in the Linux kernel's ksmbd module was due to the smb2_set_ea function performing buffer validation without accounting for the null terminator byte in the EA Name length. The validation checks omitted adding '+1' for the null terminator, potentially causing buffer size miscalculations. The patch fixes this by explicitly including the null terminator size in the EA length calculation, ensuring accurate buffer validation and preventing potential memory handling issues.

References

Community reviews

Loading reviews…