# CVE-2025-10823: axboe fio options.c str_buffer_pattern_cb null pointer dereference

> A local attacker can cause a denial of service in the fio benchmarking tool via a null pointer dereference in the str_buffer_pattern_cb function.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 22 Sep 2025
- **Updated:** 23 Sep 2025
- **Also known as:** AZL-67625, AZL-67664, DEBIAN-CVE-2025-10823, GHSA-fg45-43v5-3rqm, UBUNTU-CVE-2025-10823

## What is CVE-2025-10823?

CVE-2025-10823 is a medium-severity vulnerability in axboe fio, published on 22 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in axboe fio up to 3.41. This affects the function str_buffer_pattern_cb of the file options.c. Performing manipulation results in null pointer dereference. The attack must be initiated from a local position. The exploit has been made public and could be used.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2025-10823?


## How do I fix CVE-2025-10823?

Upgrade to a fixed version.

## Is CVE-2025-10823 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10823 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10823 and fix it if it is affected.

What it is: CVE-2025-10823 is a medium-severity vulnerability in axboe fio, published on 22 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10823 exists.

Affected product: axboe fio. 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-2025-10823/ (Markdown: https://insights.sbomify.com/CVE-2025-10823/index.md)
```

## Sources

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

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