# CVE-2026-72033: orangefs: keep the readdir entry size 64-bit in fill_from_part()

> A 32-bit truncation in OrangeFS readdir handling causes an out-of-bounds read, leading to a kernel crash.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-72033, DEBIAN-CVE-2026-72033, GHSA-36xg-4chx-xvwp, UBUNTU-CVE-2026-72033

## What is CVE-2026-72033?

CVE-2026-72033 is a critical vulnerability in Linux, published on 15 Aug 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:

orangefs: keep the readdir entry size 64-bit in fill_from_part()

fill_from_part() computes the size of a directory entry in size_t but
stores it in a __u32. An entry length near U32_MAX wraps it to a small
value, bypasses the bounds check, and is then used to index the entry,
reading far past the directory part -- an out-of-bounds read that oopses
the kernel.

Compute the size as a u64 so it cannot truncate; the bounds check then
rejects the entry. The trailer is supplied by the userspace client.

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


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

Apply the vendor's patch.

## Is CVE-2026-72033 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72033 is a critical vulnerability in Linux, published on 15 Aug 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-72033 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-72033/ (Markdown: https://insights.sbomify.com/CVE-2026-72033/index.md)
```

## Sources

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

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