dbcve.org
NULL Pointer DereferenceWeakness · CWE-476

CVE-2026-30656

HIGH · 7.5 CVSS v3.1 Published 2026-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A NULL pointer dereference vulnerability exists in fio (Flexible I/O Tester) v3.41 when parsing job files containing the fdp_pli option. The callback function str_fdp_pli_cb() does not validate the input pointer and calls strdup() on a NULL value when the option is specified without an argument. This results in a segmentation fault and process crash.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A NULL pointer dereference vulnerability exists in fio v3.41 where the str_fdp_pli_cb() callback function fails to validate the input pointer before passing it to strdup(). When the fdp_pli option is specified in a job file without an argument, the NULL pointer is dereferenced, causing a segmentation fault and process crash.

MitigationAvoid using job files that contain the fdp_pli option without a valid argument, or upgrade to a patched version of fio when available. Validate all job files before processing.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed fio version
    Run 'fio --version' or 'fio -v' to obtain the version number
    Affected if Version is exactly 3.41 (the only version listed as affected)
  2. Locate job files used by fio
    Search for .fio or job file configuration files in your workflow, typically with extensions like .job, .ini, or as inline job definitions
    Affected if Job files exist and are used with fio
  3. Inspect job files for fdp_pli option usage
    Search within job files for the string 'fdp_pli' using grep or text search (e.g., 'grep -r fdp_pli /path/to/jobfiles')
    Affected if Any job file contains the 'fdp_pli' option
  4. Verify fdp_pli option has an argument
    Examine each found fdp_pli entry; valid usage should be 'fdp_pli=<value>' where <value> is present. If you find 'fdp_pli' with nothing after the equals sign or standing alone without an argument, this is the vulnerable condition
    Affected if Any job file contains 'fdp_pli' without a following argument (empty or missing value after '=')

You are affected if you run fio version 3.41 AND use job files that specify the fdp_pli option without providing a value argument.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Avoid using job files that contain the fdp_pli option without a valid argument, or upgrade to a patched version of fio when available. Validate all job files before processing.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-30656 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-30656 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data