# CVE-2026-46078: erofs: fix the out-of-bounds nameoff handling for trailing dirents

> A crafted EROFS filesystem can trigger an integer underflow leading to out-of-bounds reads, potentially causing denial of service or information disclosure.

- **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:** 27 May 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-88632, BELL-CVE-2026-46078, DEBIAN-CVE-2026-46078, GHSA-4rmv-8gm3-jwx2, ROOT-OS-DEBIAN-11-CVE-2026-46078, ROOT-OS-DEBIAN-12-CVE-2026-46078, ROOT-OS-UBUNTU-2204-CVE-2026-46078, ROOT-OS-UBUNTU-2404-CVE-2026-46078, UBUNTU-CVE-2026-46078

## What is CVE-2026-46078?

CVE-2026-46078 is a high-severity vulnerability in Linux kernel, published on 27 May 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:

erofs: fix the out-of-bounds nameoff handling for trailing dirents

Currently we already have boundary-checks for nameoffs, but the trailing
dirents are special since the namelens are calculated with strnlen()
with unchecked nameoffs.

If a crafted EROFS has a trailing dirent with nameoff >= maxsize,
maxsize - nameoff can underflow, causing strnlen() to read past the
directory block.

nameoff0 should also be verified to be a multiple of
`sizeof(struct erofs_dirent)` as well [1].

[1] https://sashiko.dev/#/patchset/20260416063511.3173774-1-hsiangkao%40linux.alibaba.com

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2026-46078 being exploited?

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

What it is: CVE-2026-46078 is a high-severity vulnerability in Linux kernel, published on 27 May 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-46078 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-46078/ (Markdown: https://insights.sbomify.com/CVE-2026-46078/index.md)
```

## Sources

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

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