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

> A buffer validation error in the Linux kernel's ksmbd SMB server allows attackers to trigger memory corruption via crafted Extended Attributes.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jan 2026
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-74312, BELL-CVE-2025-68806, DEBIAN-CVE-2025-68806, GHSA-4wfq-6xp5-vp47, ROOT-OS-DEBIAN-12-CVE-2025-68806, ROOT-OS-DEBIAN-13-CVE-2025-68806, ROOT-OS-UBUNTU-2204-CVE-2025-68806, ROOT-OS-UBUNTU-2404-CVE-2025-68806, UBUNTU-CVE-2025-68806

## What is CVE-2025-68806?

CVE-2025-68806 is a high-severity memory corruption vulnerability in Linux, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2025-68806?


## How do I fix CVE-2025-68806?

Apply the vendor's patch.

## Is CVE-2025-68806 being exploited?

There is no known exploitation of CVE-2025-68806 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68806 and fix it if it is affected.

What it is: CVE-2025-68806 is a high-severity memory corruption vulnerability in Linux, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68806 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68806/ (Markdown: https://insights.sbomify.com/CVE-2025-68806/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68806
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68806
- OSV: https://osv.dev/vulnerability/CVE-2025-68806

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68806/
Summaries are generated and may contain mistakes; the official description above is the record.