# CVE-2023-4130: ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea()

> A flaw in the Linux kernel's ksmbd module allows attackers to cause denial of service or potentially execute code via improper buffer length validation in SMB2 requests.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Aug 2025
- **Updated:** 15 Aug 2026
- **Also known as:** BELL-CVE-2023-4130, DEBIAN-CVE-2023-4130, GHSA-3ccm-2cr5-453p, UBUNTU-CVE-2023-4130

## What is CVE-2023-4130?

CVE-2023-4130 is a high-severity vulnerability in Linux kernel, published on 16 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

ksmbd: fix wrong next length validation of ea buffer in smb2_set_ea()

There are multiple smb2_ea_info buffers in FILE_FULL_EA_INFORMATION request
from client. ksmbd find next smb2_ea_info using ->NextEntryOffset of
current smb2_ea_info. ksmbd need to validate buffer length Before
accessing the next ea. ksmbd should check buffer length using buf_len,
not next variable. next is the start offset of current ea that got from
previous ea.

## Which versions are affected by CVE-2023-4130?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2023-4130?

Apply the vendor's patch.

## Is CVE-2023-4130 being exploited?

There is no known exploitation of CVE-2023-4130 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-2023-4130 and fix it if it is affected.

What it is: CVE-2023-4130 is a high-severity vulnerability in Linux kernel, published on 16 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-4130 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-2023-4130/ (Markdown: https://insights.sbomify.com/CVE-2023-4130/index.md)
```

## Sources

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

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