Skip to main content
VulnerabilityPublished

CVE-2025-10824: axboe fio · Use After Free

Affects axboe fioSource CVE Database V5

0

Public exploit available · CVSS 4.8 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
4.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
axboe fioAffected
  • 3.0 – 3.41
42 affected builds
Fixed in–

AI-suggested

  1. Restrict local access to systems running fio to trusted and authorized personnel only, minimizing the attack surface.
  2. Implement strict user privilege management and isolation on machines used for storage testing to prevent unauthorized local exploitation.
  3. Monitor and audit usage of fio, especially the parsing of job configuration files, to detect anomalous or malicious activity.
  4. Use containerization or sandboxing techniques to isolate fio execution environments, limiting the impact of potential memory corruption.
  5. Regularly check for vendor updates or patches addressing CVE-2025-10824 and apply them promptly once available.
  6. As a temporary workaround, consider validating and sanitizing job configuration files externally before use to avoid triggering the vulnerable code paths.
  7. Educate system administrators and developers about the vulnerability and the importance of secure configuration management.
  8. Employ endpoint detection and response (EDR) tools to detect suspicious local activity that could indicate exploitation attempts. These targeted measures go beyond generic advice by focusing on access control, environment isolation, and proactive monitoring specific to fio usage contexts.

Description

A vulnerability was determined in axboe fio up to 3.41. This impacts the function __parse_jobs_ini of the file init.c. Executing manipulation can lead to use after free. The attack needs to be launched locally. The exploit has been publicly disclosed and may be utilized.

References

Community reviews

Loading reviews…