Powerscale OnefsOperating system · Dell

CVE-2025-30101

MEDIUM · 6.3 CVSS v3.1 Published 2025-05-08
Fix available
A fix is available. Upgrade to 9.10.1.2 or later.
See remediation →
65/100
Remediation priority · Elevated
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
Dell PowerScale OneFS, versions 9.8.0.0 through 9.10.1.0, contain a time-of-check time-of-use (TOCTOU) race condition vulnerability. An unauthenticated attacker with local access could potentially exploit this vulnerability, leading to denial of service and information tampering.

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 · moderate confidence

Dell PowerScale OneFS versions 9.8.0.0 through 9.10.1.0 contain a time-of-check time-of-use (TOCTOU) race condition vulnerability. An unauthenticated attacker with local physical or console access can exploit the time gap between a security check and resource use, potentially causing denial of service and information tampering.

MitigationApply Dell-provided patches to upgrade PowerScale OneFS beyond version 9.10.1.0. Until patches are applied, restrict local physical and console access to the storage system and monitor for suspicious local access attempts.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Powerscale OnefsOperating system
Affected:>= 9.8.0.0, < 9.10.1.2

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
Local
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/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 PowerScale OneFS version
    Run 'isi version' or 'isi cluster nodes' from the command line to display the installed OneFS version
    Affected if The displayed version falls between 9.8.0.0 and 9.10.1.0 inclusive, or shows 9.10.1.1 or lower
  2. Confirm version is within vulnerable range
    Compare the installed version number to the affected range: versions 9.8.0.0 through 9.10.1.0 are vulnerable. Versions 9.10.1.2 and later are not affected
    Affected if Installed version is 9.8.0.0, 9.8.0.x, 9.9.x.x, 9.10.0.x, 9.10.1.0, or 9.10.1.1
  3. Assess physical/console access exposure
    Review whether the system has untrusted local physical access or exposed console ports. Check network segmentation and physical security controls around the storage array
    Affected if Untrusted individuals have or could obtain local physical or console access to the PowerScale nodes
  4. Review system audit logs for console access
    Examine /var/log/ messages and isi audit logs for unusual or unauthorized console login attempts, especially during maintenance windows or after-hours activity
    Affected if Unexpected or unauthorized console access events are found in system logs

You are affected if your PowerScale OneFS version is 9.8.0.0 through 9.10.1.1 and untrusted local physical or console access to the system is possible.

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.

dbcve · scoped
Upgrade available Upgrade to 9.10.1.2 or later
Fixed in 9.10.1.2
Interim mitigation

Apply Dell-provided patches to upgrade PowerScale OneFS beyond version 9.10.1.0. Until patches are applied, restrict local physical and console access to the storage system and monitor for suspicious local access attempts.

Recommended fix Moderate confidence

9.10.1.2 or later

  1. Review the Dell PowerScale OneFS upgrade documentation at dell.com/support
  2. Plan upgrade during maintenance window given potential for denial of service
  3. Download OneFS version 9.10.1.2 or later from Dell support portal
  4. Follow standard OneFS upgrade procedure: backup configuration, verify cluster health, apply upgrade
  5. After upgrade, verify cluster is operational and the vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Powerscale Onefs Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,960
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2025-30101 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