# CVE-2026-93816: f2fs: validate inline dentry name lengths before conversion

> A corrupted f2fs image can cause out-of-bounds reads during inline dentry conversion, potentially leading to system crashes or code execution.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 3 Oct 2026
- **Also known as:** AZL-104006, BELL-CVE-2026-93816, DEBIAN-CVE-2026-93816, GHSA-g6g4-c2jh-p7hg, UBUNTU-CVE-2026-93816

## What is CVE-2026-93816?

CVE-2026-93816 is a high-severity memory corruption vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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

f2fs: validate inline dentry name lengths before conversion

Inline dentry conversion copies names out of the inline dentry area
before checking that each recorded name length fits in the available
filename slots.

A corrupted image can therefore make the conversion path read past
the inline filename storage while building the regular dentry block.

Validate each inline dentry name length against the inline filename
area before copying it.

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


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

Apply the vendor's patch.

## Is CVE-2026-93816 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93816 is a high-severity memory corruption vulnerability in Linux, published on 24 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-93816 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-2026-93816/ (Markdown: https://insights.sbomify.com/CVE-2026-93816/index.md)
```

## Sources

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

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