# CVE-2026-89497: orangefs: skip leading spaces before parsing client debug masks

> A buffer overflow in the Linux kernel's OrangeFS client allows attackers to write past allocated memory, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 11 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-100181, BELL-CVE-2026-89497, DEBIAN-CVE-2026-89497, GHSA-3799-qp69-xpqm, UBUNTU-CVE-2026-89497

## What is CVE-2026-89497?

CVE-2026-89497 is a high-severity memory corruption vulnerability in Linux, published on 11 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:

orangefs: skip leading spaces before parsing client debug masks

orangefs_prepare_cdm_array() sizes each client debug keyword buffer
with strcspn(cds_head, " "), but then parses the keyword with %s. The
%s conversion skips leading whitespace, while strcspn() does not.

If a client debug entry starts with a space, the allocation can be sized
for an empty keyword while sscanf() copies the following non-empty token.
This can write past the end of the allocated keyword buffer.

Skip leading spaces before computing the keyword length so the allocation
matches the string parsed by sscanf().

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


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

Apply the vendor's patch.

## Is CVE-2026-89497 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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