# CVE-2026-89838: f2fs: limit recovery filename logging to stored length

> An attacker can read adjacent kernel memory via F2FS recovery logs due to missing length checks on non-null-terminated filenames.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-101139, BELL-CVE-2026-89838, DEBIAN-CVE-2026-89838, GHSA-jfgp-78p5-g7hq, UBUNTU-CVE-2026-89838

## What is CVE-2026-89838?

CVE-2026-89838 is a high-severity vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

f2fs: limit recovery filename logging to stored length

F2FS stores recovery filenames as a length plus a fixed-size i_name
buffer.  The buffer is not NUL-terminated, but recover_inode() and
recover_dentry() print it with %s.

For a 255-byte filename, recovery logging can read past i_name into the
following raw inode fields.

Print the name with a precision bounded by i_namelen and F2FS_NAME_LEN.

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


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

Apply the vendor's patch.

## Is CVE-2026-89838 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89838 is a high-severity vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89838 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-89838/ (Markdown: https://insights.sbomify.com/CVE-2026-89838/index.md)
```

## Sources

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

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