# CVE-2026-31612: ksmbd: validate EaNameLength in smb2_get_ea()

> A missing length validation in the Linux kernel's ksmbd module allows attackers to leak uninitialized heap memory via crafted SMB2 requests.

- **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:** 24 Apr 2026
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-83783, BELL-CVE-2026-31612, DEBIAN-CVE-2026-31612, GHSA-mgh3-34fv-3j84, ROOT-OS-DEBIAN-12-CVE-2026-31612, ROOT-OS-UBUNTU-2204-CVE-2026-31612, ROOT-OS-UBUNTU-2404-CVE-2026-31612, UBUNTU-CVE-2026-31612

## What is CVE-2026-31612?

CVE-2026-31612 is a high-severity vulnerability in Linux kernel, published on 24 Apr 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: validate EaNameLength in smb2_get_ea()

smb2_get_ea() reads ea_req->EaNameLength from the client request and
passes it directly to strncmp() as the comparison length without
verifying that the length of the name really is the size of the input
buffer received.

Fix this up by properly checking the size of the name based on the value
received and the overall size of the request, to prevent a later
strncmp() call to use the length as a "trusted" size of the buffer.
Without this check, uninitialized heap values might be slowly leaked to
the client.

## Which versions are affected by CVE-2026-31612?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-31612?

Apply the vendor's patch.

## Is CVE-2026-31612 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-31612 and fix it if it is affected.

What it is: CVE-2026-31612 is a high-severity vulnerability in Linux kernel, published on 24 Apr 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-2026-31612 in the wild and no public exploit code.

Affected product: Linux kernel. 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-2026-31612/ (Markdown: https://insights.sbomify.com/CVE-2026-31612/index.md)
```

## Sources

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

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